Devices, methods, and graphical user interfaces for displaying media items shared from distinct applications

ABSTRACT

A computer system receives, by a first application, a plurality of shared media items and receives a request to display a view of a media application that includes the media library that includes a first plurality of media items. The computer system displays a collection of media items in the media application that are selected based on first criteria. Displaying the collection of media items includes displaying a second plurality of media items selected from the media library based on the first criteria. In accordance with a determination that a first shared media item from a set of one or media items that have not been added to the media library meets display criteria, the display criteria including the first criteria, displaying the first shared media item in the collection of media items concurrently with the second plurality of media items.

RELATED APPLICATIONS

This claims priority to U.S. Provisional Patent Application No.63/189,648, filed on May 17, 2021, which is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that display media items in an application,including media items that are shared using an application distinct fromthe application that displays the media items.

BACKGROUND

The use of computer systems for sharing and storing media items hasincreased significantly in recent years. Devices allow users to sharemany different types of media items with other individuals using avariety of methods, including using different communication applicationsof a user's device. While it is easy to send and receive media itemsusing communication applications, typically, a separate mediaapplication is used to view, edit, and save media items that are sharedwith the user so that the user is enabled to access and view the sharedmedia items on the user's device within the media application.

But methods for transferring media items from a communicationapplication in which the media items are shared to a media applicationin which the shared media items are to be displayed are cumbersome andinefficient. For example, using a sequence of inputs to select one ormore user interface objects and perform one or more actions on theselected user interface objects is tedious and creates a significantcognitive burden on a user. In addition, these methods take longer thannecessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for automatically displaying mediaitems from a communication application in which media items are sharedin a distinct media application for viewing and saving the media items.For example, electronic devices that automatically display the sharedmedia items in the media application without requiring user input,improve the user experience and allow the user to view and save mediaitems that have been shared with the user within the media applicationwithout the user requesting to individually transfer each media itemfrom the communication application to the media application. Suchmethods and interfaces reduce the number, extent, and/or nature of theinputs from a user and produce a more efficient human-machine interface.For battery-operated devices, such methods and interfaces conserve powerand increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touch-sensitive surface, implemented, forexample, with a touch pad. In some embodiments, the device has atouch-sensitive display (also known as a “touch screen” or “touch-screendisplay”) that includes a touch-sensitive surface. In some embodiments,the device has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, spreadsheet making, game playing,telephoning, video conferencing, e-mailing, instant messaging, workoutsupport, digital photographing, digital videoing, web browsing, digitalmusic playing, note taking, and/or digital video playing. Executableinstructions for performing these functions are, optionally, included ina non-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at a computersystem that is in communication with a display generation component andone or more input devices. The method includes receiving, by a firstapplication, a plurality of shared media items and after receiving theplurality of shared media items, receiving, via the one or more inputdevices, a request to display a view of a media application. The mediaapplication includes a media library that includes a first plurality ofmedia items, and the plurality of shared media items includes a set ofone or more media items that have not been added to the media library.The method includes, in response to receiving the request to display theview of the media application, displaying, via the display generationcomponent, a collection of media items in the media application that areselected based on first criteria. Displaying the collection of mediaitems includes displaying a second plurality of media items selectedfrom the media library based on the first criteria and, in accordancewith a determination that a first shared media item from the set of oneor media items that have not been added to the media library meetsdisplay criteria, the display criteria including the first criteria,displaying the first shared media item in the collection of media itemsconcurrently with the second plurality of media items, wherein the firstshared media item is visually distinguished from the second plurality ofmedia items based on a visual feature that is separate from content ofthe first shared media item.

In accordance with some embodiments, a method is performed at a computersystem that is in communication with a display generation component andone or more input devices. The method includes receiving, by a firstapplication, a plurality of shared media items. The method includes,after receiving the plurality of shared media items, receiving, via theone or more input devices, a request to search a media library of asecond application that is different from the first application formedia items in the media library that meet search criteria. The methodfurther includes, in response to receiving the request to search themedia library, concurrently displaying, via the display generationcomponent, two or more media items that meet the search criteria. Thetwo or more media items include: one or more media items from the medialibrary of the second application that meet the search criteria, and oneor more of the shared media items that are not stored within the medialibrary of the second application and that meet the search criteria.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensities of contacts with the touch-sensitive surface,optionally one or more tactile output generators, one or moreprocessors, and memory storing one or more programs; the one or moreprograms are configured to be executed by the one or more processors andthe one or more programs include instructions for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a computer readable storage medium hasstored therein instructions, which, when executed by an electronicdevice with a display, a touch-sensitive surface, optionally one or moresensors to detect intensities of contacts with the touch-sensitivesurface, and optionally one or more tactile output generators, cause thedevice to perform or cause performance of the operations of any of themethods described herein. In accordance with some embodiments, agraphical user interface on an electronic device with a display, atouch-sensitive surface, optionally one or more sensors to detectintensities of contacts with the touch-sensitive surface, optionally oneor more tactile output generators, a memory, and one or more processorsto execute one or more programs stored in the memory includes one ormore of the elements displayed in any of the methods described herein,which are updated in response to inputs, as described in any of themethods described herein. In accordance with some embodiments, anelectronic device includes: a display, a touch-sensitive surface,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, and optionally one or more tactile outputgenerators; and means for performing or causing performance of theoperations of any of the methods described herein. In accordance withsome embodiments, an information processing apparatus, for use in anelectronic device with a display, a touch-sensitive surface, optionallyone or more sensors to detect intensities of contacts with thetouch-sensitive surface, and optionally one or more tactile outputgenerators, includes means for performing or causing performance of theoperations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, optionally one or more tactile outputgenerators, optionally one or more device orientation sensors, andoptionally an audio system, are provided with improved methods andinterfaces for displaying shared media items in a media application,thereby increasing the effectiveness, efficiency, and user satisfactionwith such devices. Such methods and interfaces may complement or replaceconventional methods for displaying shared media items in a mediaapplication.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example of a user interface that includes a menuof applications on a portable multifunction device, in accordance withsome embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 4C-4E illustrate examples of dynamic intensity thresholds inaccordance with some embodiments.

FIGS. 5A-5AQ illustrate example user interfaces for concurrentlydisplaying media items in an application with shared media items thatare received via a distinct application, in accordance with someembodiments.

FIGS. 6A-6P illustrate example user interfaces for displaying searchresults for media items in an application, in accordance with someembodiments.

FIGS. 7A-7E are flow diagrams of a process for concurrently displayingmedia items in an application with shared media items that are receivedvia a distinct application in accordance with some embodiments.

FIGS. 8A-8B are flow diagrams of a process for displaying search resultsfor media items in an application, including concurrently displayingmedia items saved in the application with shared media items that arereceived via a distinct application in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Accordingly, a method is provided for automatically displaying mediaitems from a communication application in which media items are sharedin a distinct media application for viewing and saving the media items.For example, electronic devices that automatically display the sharedmedia items in the media application without requiring user input,improves the user experience and allows the user to view and save mediaitems that have been shared with the user within the media applicationwithout the user requesting to individual transfer each media item fromthe communication application to the media application.

Below, FIGS. 1A-1B, 2, and 3 provide a description of example devices.FIGS. 4A-4B, 5A-5AQ and 6A-6P illustrate example user interfaces forconcurrently displaying media items in an application with shared mediaitems that are received via a distinct application. FIGS. 7A-7Eillustrate a flow diagram of a method of concurrently displaying mediaitems in an application with shared media items that are received via adistinct application. FIGS. 8A-8B illustrate a flow diagram of a methodof displaying search results, including concurrently displaying mediaitems in an application with shared media items that are received via adistinct application. The user interfaces in FIGS. 5A-5AQ and 6A-6P areused to illustrate the processes in FIGS. 7A-7E, and 8A-8B.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, California. Other portableelectronic devices, such as laptops or tablet computers withtouch-sensitive surfaces (e.g., touch-screen displays and/or touchpads),are, optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a note taking application, a drawing application,a presentation application, a word processing application, a websitecreation application, a disk authoring application, a spreadsheetapplication, a gaming application, a telephone application, a videoconferencing application, an e-mail application, an instant messagingapplication, a workout support application, a photo managementapplication, a digital camera application, a digital video cameraapplication, a web browsing application, a digital music playerapplication, and/or a digital video player application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensities of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user. Using tactile outputs toprovide haptic feedback to a user enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, a tactile output pattern specifies characteristicsof a tactile output, such as the amplitude of the tactile output, theshape of a movement waveform of the tactile output, the frequency of thetactile output, and/or the duration of the tactile output.

When tactile outputs with different tactile output patterns aregenerated by a device (e.g., via one or more tactile output generatorsthat move a moveable mass to generate tactile outputs), the tactileoutputs may invoke different haptic sensations in a user holding ortouching the device. While the sensation of the user is based on theuser's perception of the tactile output, most users will be able toidentify changes in waveform, frequency, and amplitude of tactileoutputs generated by the device. Thus, the waveform, frequency andamplitude can be adjusted to indicate to the user that differentoperations have been performed. As such, tactile outputs with tactileoutput patterns that are designed, selected, and/or engineered tosimulate characteristics (e.g., size, material, weight, stiffness,smoothness, etc.); behaviors (e.g., oscillation, displacement,acceleration, rotation, expansion, etc.); and/or interactions (e.g.,collision, adhesion, repulsion, attraction, friction, etc.) of objectsin a given environment (e.g., a user interface that includes graphicalfeatures and objects, a simulated physical environment with virtualboundaries and virtual objects, a real physical environment withphysical boundaries and physical objects, and/or a combination of any ofthe above) will, in some circumstances, provide helpful feedback tousers that reduces input errors and increases the efficiency of theuser's operation of the device. Additionally, tactile outputs are,optionally, generated to correspond to feedback that is unrelated to asimulated physical characteristic, such as an input threshold or aselection of an object. Such tactile outputs will, in somecircumstances, provide helpful feedback to users that reduces inputerrors and increases the efficiency of the user's operation of thedevice.

In some embodiments, a tactile output with a suitable tactile outputpattern serves as a cue for the occurrence of an event of interest in auser interface or behind the scenes in a device. Examples of the eventsof interest include activation of an affordance (e.g., a real or virtualbutton, or toggle switch) provided on the device or in a user interface,success or failure of a requested operation, reaching or crossing aboundary in a user interface, entry into a new state, switching of inputfocus between objects, activation of a new mode, reaching or crossing aninput threshold, detection or recognition of a type of input or gesture,etc. In some embodiments, tactile outputs are provided to serve as awarning or an alert for an impending event or outcome that would occurunless a redirection or interruption input is timely detected. Tactileoutputs are also used in other contexts to enrich the user experience,improve the accessibility of the device to users with visual or motordifficulties or other accessibility needs, and/or improve efficiency andfunctionality of the user interface and/or the device. Tactile outputsare optionally accompanied with audio outputs and/or visible userinterface changes, which further enhance a user's experience when theuser interacts with a user interface and/or the device, and facilitatebetter conveyance of information regarding the state of the userinterface and/or the device, and which reduce input errors and increasethe efficiency of the user's operation of the device.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2 ) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2 ).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds to userinterface objects. As used herein, the term “affordance” refers to auser-interactive graphical user interface object (e.g., a graphical userinterface object that is configured to respond to inputs directed towardthe graphical user interface object). Examples of user-interactivegraphical user interface objects include, without limitation, a button,slider, icon, selectable menu item, switch, hyperlink, or other userinterface control.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based on hapticand/or tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In some embodiments, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In some embodiments, projected mutual capacitance sensingtechnology is used, such as that found in the iPhone®, iPod Touch®, andiPad® from Apple Inc. of Cupertino, California.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. In someembodiments, tactile output generator(s) 167 include one or moreelectroacoustic devices such as speakers or other audio componentsand/or electromechanical devices that convert energy into linear motionsuch as a motor, solenoid, electroactive polymer, piezoelectricactuator, electrostatic actuator, or other tactile output generatingcomponent (e.g., a component that converts electrical signals intotactile outputs on the device). Tactile output generator(s) 167 receivetactile feedback generation instructions from haptic feedback module 133and generates tactile outputs on device 100 that are capable of beingsensed by a user of device 100. In some embodiments, at least onetactile output generator is collocated with, or proximate to, atouch-sensitive surface (e.g., touch-sensitive display system 112) and,optionally, generates a tactile output by moving the touch-sensitivesurface vertically (e.g., in/out of a surface of device 100) orlaterally (e.g., back and forth in the same plane as a surface of device100). In some embodiments, at least one tactile output generator sensoris located on the back of device 100, opposite touch-sensitive displaysystem 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled with peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled with an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch-screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3 . Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, California. In some embodiments, theexternal port is a Lightning connector that is the same as, or similarto and/or compatible with the Lightning connector used in some iPhone®,iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes varioussoftware components for performing various operations related todetection of contact (e.g., by a finger or by a stylus), such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts or stylus contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

In some embodiments, detecting a finger tap gesture depends on thelength of time between detecting the finger-down event and the finger-upevent, but is independent of the intensity of the finger contact betweendetecting the finger-down event and the finger-up event. In someembodiments, a tap gesture is detected in accordance with adetermination that the length of time between the finger-down event andthe finger-up event is less than a predetermined value (e.g., less than0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensityof the finger contact during the tap meets a given intensity threshold(greater than a nominal contact-detection intensity threshold), such asa light press or deep press intensity threshold. Thus, a finger tapgesture can satisfy particular input criteria that do not require thatthe characteristic intensity of a contact satisfy a given intensitythreshold in order for the particular input criteria to be met. Forclarity, the finger contact in a tap gesture typically needs to satisfya nominal contact-detection intensity threshold, below which the contactis not detected, in order for the finger-down event to be detected. Asimilar analysis applies to detecting a tap gesture by a stylus or othercontact. In cases where the device is capable of detecting a finger orstylus contact hovering over a touch sensitive surface, the nominalcontact-detection intensity threshold optionally does not correspond tophysical contact between the finger or stylus and the touch sensitivesurface.

The same concepts apply in an analogous manner to other types ofgestures. For example, a swipe gesture, a pinch gesture, a depinchgesture, and/or a long press gesture are optionally detected based onthe satisfaction of criteria that are either independent of intensitiesof contacts included in the gesture, or do not require that contact(s)that perform the gesture reach intensity thresholds in order to berecognized. For example, a swipe gesture is detected based on an amountof movement of one or more contacts; a pinch gesture is detected basedon movement of two or more contacts towards each other; a depinchgesture is detected based on movement of two or more contacts away fromeach other; and a long press gesture is detected based on a duration ofthe contact on the touch-sensitive surface with less than a thresholdamount of movement. As such, the statement that particular gesturerecognition criteria do not require that the intensity of the contact(s)meet a respective intensity threshold in order for the particulargesture recognition criteria to be met means that the particular gesturerecognition criteria are capable of being satisfied if the contact(s) inthe gesture do not reach the respective intensity threshold, and arealso capable of being satisfied in circumstances where one or more ofthe contacts in the gesture do reach or exceed the respective intensitythreshold. In some embodiments, a tap gesture is detected based on adetermination that the finger-down and finger-up event are detectedwithin a predefined time period, without regard to whether the contactis above or below the respective intensity threshold during thepredefined time period, and a swipe gesture is detected based on adetermination that the contact movement is greater than a predefinedmagnitude, even if the contact is above the respective intensitythreshold at the end of the contact movement. Even in implementationswhere detection of a gesture is influenced by the intensity of contactsperforming the gesture (e.g., the device detects a long press morequickly when the intensity of the contact is above an intensitythreshold or delays detection of a tap input when the intensity of thecontact is higher), the detection of those gestures does not requirethat the contacts reach a particular intensity threshold so long as thecriteria for recognizing the gesture can be met in circumstances wherethe contact does not reach the particular intensity threshold (e.g.,even if the amount of time that it takes to recognize the gesturechanges).

Contact intensity thresholds, duration thresholds, and movementthresholds are, in some circumstances, combined in a variety ofdifferent combinations in order to create heuristics for distinguishingtwo or more different gestures directed to the same input element orregion so that multiple different interactions with the same inputelement are enabled to provide a richer set of user interactions andresponses. The statement that a particular set of gesture recognitioncriteria do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the particular gesturerecognition criteria to be met does not preclude the concurrentevaluation of other intensity-dependent gesture recognition criteria toidentify other gestures that do have a criteria that is met when agesture includes a contact with an intensity above the respectiveintensity threshold. For example, in some circumstances, first gesturerecognition criteria for a first gesture—which do not require that theintensity of the contact(s) meet a respective intensity threshold inorder for the first gesture recognition criteria to be met—are incompetition with second gesture recognition criteria for a secondgesture—which are dependent on the contact(s) reaching the respectiveintensity threshold. In such competitions, the gesture is, optionally,not recognized as meeting the first gesture recognition criteria for thefirst gesture if the second gesture recognition criteria for the secondgesture are met first. For example, if a contact reaches the respectiveintensity threshold before the contact moves by a predefined amount ofmovement, a deep press gesture is detected rather than a swipe gesture.Conversely, if the contact moves by the predefined amount of movementbefore the contact reaches the respective intensity threshold, a swipegesture is detected rather than a deep press gesture. Even in suchcircumstances, the first gesture recognition criteria for the firstgesture still do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the first gesturerecognition criteria to be met because if the contact stayed below therespective intensity threshold until an end of the gesture (e.g., aswipe gesture with a contact that does not increase to an intensityabove the respective intensity threshold), the gesture would have beenrecognized by the first gesture recognition criteria as a swipe gesture.As such, particular gesture recognition criteria that do not requirethat the intensity of the contact(s) meet a respective intensitythreshold in order for the particular gesture recognition criteria to bemet will (A) in some circumstances ignore the intensity of the contactwith respect to the intensity threshold (e.g. for a tap gesture) and/or(B) in some circumstances still be dependent on the intensity of thecontact with respect to the intensity threshold in the sense that theparticular gesture recognition criteria (e.g., for a long press gesture)will fail if a competing set of intensity-dependent gesture recognitioncriteria (e.g., for a deep press gesture) recognize an input ascorresponding to an intensity-dependent gesture before the particulargesture recognition criteria recognize a gesture corresponding to theinput (e.g., for a long press gesture that is competing with a deeppress gesture for recognition).

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions (e.g., instructions used by haptic feedbackcontroller 161) to produce tactile outputs using tactile outputgenerator(s) 167 at one or more locations on device 100 in response touser interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages, and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and video andmusic player module 152, workout support module 142 includes executableinstructions to create workouts (e.g., with time, distance, and/orcalorie burning goals); communicate with workout sensors (in sportsdevices and smart watches); receive workout sensor data; calibratesensors used to monitor a workout; select and play music for a workout;and display, store and transmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170(e.g., in operating system 126) and a respective application 136-1(e.g., any of the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 168, and/or microphone 113 (through audiocircuitry 110). Information that peripherals interface 118 receives fromI/O subsystem 106 includes information from touch-sensitive displaysystem 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoand music player module 152. In some embodiments, object updater 177creates and updates objects used in application 136-1. For example,object updater 177 creates a new user-interface object or updates theposition of a user-interface object. GUI updater 178 updates the GUI.For example, GUI updater 178 prepares display information and sends itto graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In these embodiments, as wellas others described below, a user is enabled to select one or more ofthe graphics by making a gesture on the graphics, for example, with oneor more fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204 (sometimes called home button 204), push button 206 forpowering the device on/off and locking the device, volume adjustmentbutton(s) 208, Subscriber Identity Module (SIM) card slot 210, head setjack 212, and docking/charging external port 124. Push button 206 is,optionally, used to turn the power on/off on the device by depressingthe button and holding the button in the depressed state for apredefined time interval; to lock the device by depressing the buttonand releasing the button before the predefined time interval haselapsed; and/or to unlock the device or initiate an unlock process. Insome embodiments, device 100 also accepts verbal input for activation ordeactivation of some functions through microphone 113. Device 100 also,optionally, includes one or more contact intensity sensors 165 fordetecting intensities of contacts on touch-sensitive display system 112and/or one or more tactile output generators 167 for generating tactileoutputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) for wireless communication(s), such        as cellular and Wi-Fi signals;    -   Time;    -   a Bluetooth indicator;    -   a Battery status indicator; Tray 408 with icons for frequently        used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, labeled            “Music;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, other labels are, optionally, used forvarious application icons. In some embodiments, a label for a respectiveapplication icon includes a name of an application corresponding to therespective application icon. In some embodiments, a label for aparticular application icon is distinct from a name of an applicationcorresponding to the particular application icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3 ) that is separate from the display 450. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 inFIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to aprimary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). Inaccordance with these embodiments, the device detects contacts (e.g.,460 and 462 in FIG. 4B) with the touch-sensitive surface 451 atlocations that correspond to respective locations on the display (e.g.,in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In thisway, user inputs (e.g., contacts 460 and 462, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 451 in FIG.4B) are used by the device to manipulate the user interface on thedisplay (e.g., 450 in FIG. 4B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3A or touch-sensitive surface 451 in FIG.4B) while the cursor is over a particular user interface element (e.g.,a button, window, slider or other user interface element), theparticular user interface element is adjusted in accordance with thedetected input. In some implementations that include a touch-screendisplay (e.g., touch-sensitive display system 112 in FIG. 1A or thetouch screen in FIG. 4A) that enables direct interaction with userinterface elements on the touch-screen display, a detected contact onthe touch-screen acts as a “focus selector,” so that when an input(e.g., a press input by the contact) is detected on the touch-screendisplay at a location of a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations, focus is moved from one region of a userinterface to another region of the user interface without correspondingmovement of a cursor or movement of a contact on a touch-screen display(e.g., by using a tab key or arrow keys to move focus from one button toanother button); in these implementations, the focus selector moves inaccordance with movement of focus between different regions of the userinterface. Without regard to the specific form taken by the focusselector, the focus selector is generally the user interface element (orcontact on a touch-screen display) that is controlled by the user so asto communicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device). Insome embodiments, a focus indicator (e.g., a cursor or selectionindicator) is displayed via the display device to indicate a currentportion of the user interface that will be affected by inputs receivedfrom the one or more input devices.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms (milliseconds) in duration (e.g., 40, 100, or120 ms, depending on the magnitude of the second intensity threshold,with the delay time increasing as the second intensity thresholdincreases). This delay time helps to avoid accidental recognition ofdeep press inputs. As another example, for some “deep press” inputs,there is a reduced-sensitivity time period that occurs after the time atwhich the first intensity threshold is met. During thereduced-sensitivity time period, the second intensity threshold isincreased. This temporary increase in the second intensity thresholdalso helps to avoid accidental deep press inputs. For other deep pressinputs, the response to detection of a deep press input does not dependon time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Example factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

For example, FIG. 4C illustrates a dynamic intensity threshold 480 thatchanges over time based in part on the intensity of touch input 476 overtime. Dynamic intensity threshold 480 is a sum of two components, firstcomponent 474 that decays over time after a predefined delay time p1from when touch input 476 is initially detected, and second component478 that trails the intensity of touch input 476 over time. The initialhigh intensity threshold of first component 474 reduces accidentaltriggering of a “deep press” response, while still allowing an immediate“deep press” response if touch input 476 provides sufficient intensity.Second component 478 reduces unintentional triggering of a “deep press”response by gradual intensity fluctuations of in a touch input. In someembodiments, when touch input 476 satisfies dynamic intensity threshold480 (e.g., at point 481 in FIG. 4C), the “deep press” response istriggered.

FIG. 4D illustrates another dynamic intensity threshold 486 (e.g.,intensity threshold I_(D)). FIG. 4D also illustrates two other intensitythresholds: a first intensity threshold I_(H) and a second intensitythreshold I_(L). In FIG. 4D, although touch input 484 satisfies thefirst intensity threshold I_(H) and the second intensity threshold I_(L)prior to time p2, no response is provided until delay time p2 haselapsed at time 482. Also in FIG. 4D, dynamic intensity threshold 486decays over time, with the decay starting at time 488 after a predefineddelay time p1 has elapsed from time 482 (when the response associatedwith the second intensity threshold I_(L) was triggered). This type ofdynamic intensity threshold reduces accidental triggering of a responseassociated with the dynamic intensity threshold I_(D) immediately after,or concurrently with, triggering a response associated with a lowerintensity threshold, such as the first intensity threshold I_(H) or thesecond intensity threshold I_(L).

FIG. 4E illustrate yet another dynamic intensity threshold 492 (e.g.,intensity threshold I_(D)). In FIG. 4E, a response associated with theintensity threshold I_(L) is triggered after the delay time p2 haselapsed from when touch input 490 is initially detected. Concurrently,dynamic intensity threshold 492 decays after the predefined delay timep1 has elapsed from when touch input 490 is initially detected. So adecrease in intensity of touch input 490 after triggering the responseassociated with the intensity threshold I_(L), followed by an increasein the intensity of touch input 490, without releasing touch input 490,can trigger a response associated with the intensity threshold I_(D)(e.g., at time 494) even when the intensity of touch input 490 is belowanother intensity threshold, for example, the intensity threshold I_(L).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, (optionally) one or more tactileoutput generators for generating tactile outputs, and (optionally) oneor more sensors to detect intensities of contacts with thetouch-sensitive surface.

FIGS. 5A-5AQ and FIGS. 6A-6P illustrate example user interfaces forconcurrently displaying media items in an application with shared mediaitems that are received via a distinct application, in accordance withsome embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processesdescribed with respect to FIGS. 7A-7E and 8A-8B. For convenience ofexplanation, some of the embodiments will be discussed with reference tooperations performed on a device with a touch-sensitive display system112. In such embodiments, the focus selector is, optionally: arespective finger or stylus contact, a representative pointcorresponding to a finger or stylus contact (e.g., a centroid of arespective contact or a point associated with a respective contact), ora centroid of two or more contacts detected on the touch-sensitivedisplay system 112. However, analogous operations are, optionally,performed on a device with a display 450 and a separate touch-sensitivesurface 451 in response to detecting the contacts on the touch-sensitivesurface 451 while displaying the user interfaces shown in the figures onthe display 450, along with a focus selector.

FIGS. 5A-5AQ illustrate example user interfaces for concurrentlydisplaying media items in an application with shared media items thatare received via a distinct application in accordance with someembodiments.

FIG. 5A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments, as described with reference to FIG. 4A. FIG. 5A furtherillustrates user input 502 selecting icon 424 (e.g., Messages icon) tolaunch a messaging application (e.g., a communication application). Insome embodiments, in response to receiving user input 502, device 100opens a messaging application, as displayed in FIG. 5B.

FIG. 5B illustrates an example user interface of a messagingapplication, including a first message thread (sometimes called acommunication thread) between a user of device 100 and a second user ofa second device (e.g., Tom). For example, displaying the messagingapplication includes displaying one or more messages sent by the user ofdevice 100 (e.g., message 504-1) and/or one or more messages sent by thesecond user of the second device (e.g., messages that are received bydevice 100), such as messages 504-2 and 504-3. The one or more messagesdisplayed in the messaging application user interface are sometimescalled a conversation transcript; alternatively, the displayed messagesare a portion of a conversation transcript of a messaging session (e.g.,the first message thread) between the user of device 100 and the seconduser of the second device. In some embodiments, messages sent by theuser of device 100 appear on the right side of the message thread, andmessages received by device 100 (e.g., from Tom) are displayed on theleft side of the message thread. In some embodiments, the one or moremessages sent and/or received by device 100 include media items (e.g.,photos, videos, GIFs, audio messages, etc.). For example, message 504-3from Tom includes a photo. In some embodiments, messaging applicationfurther includes a keyboard (e.g., a soft keyboard, as described abovewith reference to Text input module 134) for entering text to compose(e.g., and send) messages.

In some embodiments, a user of device 100 responds to (e.g., sends) amessage in the messaging application, and the messaging applicationdisplays the message within the message thread (e.g., message 504-4, asshown in FIG. 5C). In some embodiments, device 100 stores the messagethread (e.g., as a conversation history) in the messaging application.

FIGS. 5D and 5D-1 illustrate additional portions of the message threadbetween the user of device 100 and Tom. For example, device 100 receivesadditional messages from Tom (e.g., message 504-5 and message 504-6).For example, as device 100 receives (e.g., and/or sends) additionalmessages, the messages are displayed below previously received and/orsent messages in the message thread. FIG. 5D illustrates another exampleof device 100 receiving a media item (e.g., a photo of planes) withinmessage 504-6.

FIG. 5D-1 illustrates that, in response to the user of device 100sending a message 504-7, message 504-7 is also displayed by themessaging application in the conversation transcript of the messagethread. In some embodiments, the displayed conversation transcriptincludes a chronologically ordered presentation of the messages in themessage thread and is scrollable by the user, e.g., using swipe gestureson the device's touch-sensitive surface, enabling the user to scroll touser-selected portions of the message thread.

FIG. 5E illustrates another example of a message 504-8 received, bydevice 100, from Tom in the messaging application. Message 504-8includes another type of media item (e.g., a GIF). It will be understoodthat any combination of media items can be received and/or sent usingthe messaging application, including photos, videos, GIFs, audiomessages, etc.

FIG. 5E-1 illustrates user input 506 selecting a back control withinmessaging application. In some embodiments, in response to detectingselection of the back control, device 100 updates display of themessaging application to show representations of a plurality of messagethreads (e.g., stored conversation histories), as illustrated in FIG.5F.

For example, FIG. 5F illustrates a plurality of representations ofmessage threads (e.g., where the representation of each message threadcorresponds to a distinct conversation history). For example, FIG. 5Fillustrates a representation of a message thread for Tom, arepresentation of a message thread for a group message, “BFF Group,” arepresentation of a message thread for Lucy, a representation of amessage thread for Sam, a representation of a message thread for Tony,and a representation of a message thread for a second group message,“Family Group.” In some embodiments, group message threads include threeor more participants, including two or more “additional” users (e.g., inaddition to the user of device 100). In some embodiments, the messagingapplication displays, for each message thread, a time indication (e.g.,a time stamp such as “1:58 PM” or “Yesterday”, etc.) of a last messagethat was received or sent in the respective message thread. In someembodiments, the user of device 100 is enabled to select arepresentation of a respective message thread (e.g., by selecting icon508, or otherwise selecting the representation of the respective messagethread) to open the message thread to view the messages in theconversation history and/or to send a new message in the selectedmessage thread.

FIG. 5G illustrates user input 510 selecting icon 508 to open themessage thread for “BFF Group.” In response to detecting selection ofthe message thread for “BFF Group,” messaging application displays aconversation history for “BFF Group,” as illustrated in FIG. 5H. Asexplained above, a group messaging thread includes two or moreadditional users (e.g., members of the group). For example, “BFF Group”includes 3 additional members (e.g., in addition to the user of device100), as indicated by “A” “B” and “C” displayed at the top of the groupmessaging thread (shown in FIG. 5H). For example, “A”, “B” and “C” arerepresentations of contacts (e.g., other users) to indicate whichindividuals are included in the group. For example, Alice (“A”), Betty(“B”), and Catherine (“C”) are included in the BFF Group message thread.In some embodiments, the representation of a respective user comprises apicture or emoticon to represent the respective user (e.g., instead ofone or more letters).

FIGS. 5H-5I illustrate a plurality of messages within the message threadfor “BFF Group.” For example, FIG. 5H illustrates a message 512-1 sentby the user of the device 100 and a plurality of messages received bydevice 100. For example, message 512-2 and message 512-3 are receivedfrom Betty (e.g., as indicated by the “B” in the circle and the textuallabel “Betty” above message 512-2). In some embodiments, in a groupmessage, messages received by device 100 include a label of which userin the group sent the message. In some embodiments, the messages sent ina group message thread are sent to each member of the group (e.g., themessages sent from Betty are sent to the user of device 100, as well asto Alice and Catherine).

FIG. 5I illustrates a plurality of messages received at device 100 fromBetty, each message including content, such as message 512-3 and 512-4,which each include a photo (e.g., image). In some embodiments, mediaitems that are received from another user via a communicationapplication (e.g., the messaging application) are referred to herein asshared media items (e.g., shared by another user with device 100). Insome embodiments, the shared media items are not automatically saved todevice 100. In some embodiments, the shared media items are storedwithin the message thread (e.g., or otherwise stored within anapplication in which the media item was shared) without being stored ina media application of device 100 (e.g., wherein the media applicationallows a user to view, edit and/or store media items). For example, asdescribed in more detail with respect to FIG. 5K, a media application isenabled to display shared media items even when the shared media itemsare not saved to a media library of the media application.

FIG. 5J illustrates an example user interface of device 100, asexplained with reference to FIGS. 4A and 5A. In some embodiments, theuser interface includes icon 428 for opening (e.g., launching,initiating execution, or resuming execution of) a photos application(e.g., corresponding to image management module 144). In someembodiments, in response to device 100 detecting user input 514 (e.g., atap input) on icon 428, the photos application is launched (e.g.,opened) and displayed on device 100, as illustrated in FIG. 5K.

FIG. 5K illustrates an example user interface of the photos application.In some embodiments, photos application stores photos (e.g., and/orvideos or other media items), including media items captured by device100, in the memory of device 100. For example, device 100 includescamera application (e.g., represented by icon 430, FIG. 5J) forcapturing photos and/or videos using device 100. In some embodiments,the photos and/or videos captured using the camera application arestored locally (e.g., within the memory of device 100) and displayedwithin the photos application. In some embodiments, the photosapplication also displays media items that are not stored locally (e.g.,within the memory of device 100). For example, the photos applicationdisplays media items that are associated with (e.g., stored using) anaccount of the user of device 100 (e.g., stored at a server system (“inthe cloud”) to be accessed by the account of the user). In someembodiments, media items that are stored locally at device 100 and/ormedia items that are stored using the account associated with the userof device 100 are referred to as media items saved to a media library ofthe user. In some embodiments, the photos application (e.g., or othermedia application) does not display one or more types of media items.For example, in some embodiments, the photos application does notdisplay GIF images files, sometimes called GIFs, and thus cannot displaythe GIF that was shared with device 100 (e.g., as described withreference to FIG. 5E). It will be understood that in some embodiments,different media applications (e.g., other than a photos application)display different types of shared media items (e.g., a Music applicationdisplays shared musical media items (e.g., songs)). In some embodiments,a single media application displays a plurality of types of shared mediaitems (e.g., the photos application displays shared photos and sharedvideos).

In some embodiments, displaying the photos application includesdisplaying an option for filtering display of one or more media items.For example, the device 100 (e.g., using the photos application) isenabled to display “All Photos” 536 (e.g., including all photos in themedia library of the user and shared content), or is able to organizephotos (e.g., photos in its media library) according to various timeperiods, such as a year, month, or day in which the media item wascaptured (e.g., device 100, using the photos application, divides thecontent into a plurality of distinct sets according to a year, month orday), and displays the media items within a respective grouping (e.g., auser is enabled to select a respective set corresponding to a respectiveyear, month or day). In some embodiments, the photos application furtherincludes navigation options to change the view within the photosapplication, including “Library” 538, “For You” 540, “Albums” 542 and“Search” 544. For example, the example user interface shown in FIG. 5Kcorresponds to the “Library” view. In some embodiments, the “Library”view displays a predetermined set of the media items in the medialibrary. In some embodiments, the “Library” view displays media itemsaccording to a date and/or time of capture of the media item. Forexample, device 100, using the photos application, sorts the media itemsto show the most recently captured media items at the top (or bottom) ofa user interface of the photos application. In some embodiments, device100 sorts the media items based on other display criteria (e.g.,relevance criteria).

In the example shown in FIG. 5K, device 100 displays a plurality ofmedia items (e.g., photos 516-531) in the photos application. In someembodiments, one or more of the photos displayed are shared photos(e.g., photos received at device 100 from another user of a distinctdevice). In some embodiments, the one or more shared photos aredisplayed concurrently with one or more photos that are not sharedphotos (e.g., one or more photos that are saved in the media library ofthe user). In some embodiments, the user is enabled to save a sharedphoto to the media library of the user. In some embodiments, after theshared photo is saved to the library of the user, the photo is no longerconsidered a shared photo. In some embodiments, after the shared photois saved to the media library of the user, the photo continues to beclassified as a shared photo, but the indication that the photo is ashared photo is hidden (e.g., while displaying the plurality of mediaitems).

For example, FIG. 5K illustrates shared photo 520 (e.g., which wasshared within messaging application by Tom, as explained with referenceto FIGS. 5D and 5D-1 ). In some embodiments, shared photo 520 isdisplayed with a sharing indication 532 to identify photo 520 as ashared photo. For example, photo 517, photo 526, photo 527, and photo529 are shared photos (e.g., that have not been saved to the medialibrary of the user), and are thus displayed with sharing indications.In some embodiments, sharing indication 532 comprises an overlay (e.g.,a translucent overlay) that is displayed over at least a portion, suchas at least one corner, of the photos (e.g., the bottom left corner). Insome embodiments, the overlay includes an indication of an applicationin which the media item was shared. For example, sharing indication 532includes an icon that corresponds to icon 424 (e.g., for the messagingapplication) and sharing indication 534 is displayed over photo 529 toindicate that photo 529 was shared using a communication applicationassociated with the envelope icon (e.g., an email application). It willbe understood that different icons may be selected to indicateinformation about the shared media item (e.g., an application in whichthe media item was shared, information about a user that shared themedia item, etc.). It will also be understood that the sharingindication could include information about an individual that shared themedia item.

In some embodiments, the sharing indication displayed with acorresponding shared media item comprises a border 546 (e.g., a frame)that is displayed around the shared media item, as illustrated in FIG.5L. In some embodiments, the border comprises a blurred visual effectthat is applied to the shared media item, and an unmodified (e.g., notblurred) version of the media item is displayed as a smaller thumbnail(e.g., as compared to the size of thumbnails of media items in the medialibrary) that fits within the border.

FIG. 5M illustrates user input 548 selecting “For You” navigation icon.In response to user input 548, device 100 updates display of photosapplication to display the user interface illustrated in FIG. 5N.

FIG. 5N illustrates a “For You” user interface in accordance with someembodiments. For example, the “For You” user interface includes aplurality of sections that display media items selected by device 100 asbeing relevant to the user. For example, the “For You” user interfaceincludes content curated (e.g., syndicated) for the user, includingdisplaying media items in “Memories” section 550 of the user interfaceand displaying media items in “Shared With You” section 556 of the userinterface. In some embodiments, “Memories” section 550 includes bothshared media items and media items that were not shared (e.g., mediaitems that are saved to the media library of the user). In someembodiments, shared media items that are displayed in “Memories” section550 are optionally displayed with an indication that the media items areshared media items, for example, by displaying the shared media itemwith border 552 and/or an indication of the user 554 that shared themedia item (e.g., “T” for Tom because photo 517 was shared by Tom usingthe messaging application). In some embodiments, “Shared With You”section 556 includes one or more shared media items, including photos526 and 527 (e.g., which are shared by Betty in BFF Group using themessaging application). In some embodiments, media items displayed inthe “Shared With You” section are not displayed with an indication thatthe media items are shared media items (e.g., without border 552 orindication of user 554) because each media item that is displayed within“Shared With You” section 556 is a shared media item (e.g., and thus themedia items do not need to be distinguished from each other).

In some embodiments, a user-selectable option to “See All” is displayedwith each section of the “For You” user interface. For example, “SeeAll” option 558 is displayed for the “Shared With You” section. FIG. 5Oillustrates receiving user input 560 (e.g., a tap input) selecting the“See All” option 558. In response to detecting selection of the “SeeAll” option 558, device 100 updates display of the user interface inwhich the shared content is displayed without displaying non-sharedcontent, as illustrated in FIG. 5P.

FIG. 5P illustrates an example user interface for viewing all of themedia items in the “Shared With You” section (e.g., a user is enabled toscroll down to continue viewing media items in the “Shared With You”section). In some embodiments, the shared media items are optionallydisplayed with sharing indication 562 (e.g., which is optionally thesame as indication 532, described in FIG. 5K, or is a sharing indicationdistinct from indication 532). In some embodiments, the shared mediaitems in the “Shared With You” user interface are displayed withoutsharing indication 562 (not shown). In some embodiments, the “SharedWith You” user interface includes display of one or more media itemsthat are not displayed in the “All Photos” view described with referenceto FIG. 5K. For example, the “All Photos” view displays one or moremedia items (e.g., shared media items) that meet display criteria (e.g.,relevance criteria) without displaying one or more media items (e.g.,shared media items) that do not meet the display criteria. For example,the display criteria is based on whether device 100 determines that themedia item is relevant to the user, including determining one or moreof, whether the user of device 100 (e.g., or a device associated withthe user of device 100) was within a predefined proximity to thelocation of where the media item was captured, whether the user ofdevice 100 is in the media item, whether an individual in the media itemappears in other media items in the media library of the user, and anyother criteria that the device 100 would use to determine whether themedia item is relevant to the user. For example, FIG. 5P illustratesshared photo 563, which was not displayed in the “All Photos” view shownin FIG. 5K (e.g., because shared photo 563 did not satisfy the displaycriteria). FIG. 5P further illustrates user input 564 (e.g., a tapinput) selecting photo 517.

In response to detecting user input 564 selecting photo 517, device 100updates display of the photo application to display an enlargedrepresentation of photo 517, as illustrated in FIG. 5Q. The updateddisplay illustrated in FIG. 5Q further includes displayed sharinginformation 566, including an indication of a user that shared theselected photo (e.g., “Shared by Tom”), a date on which the media itemwas shared (e.g., “May 3, 2021) and/or an application that was used toshare the media item (e.g., “Messages”). In some embodiments, device 100displays a user-selectable option 568 to allow the user to open theapplication in which the media item was shared (e.g., “Go to Messages”).In some embodiments, device 100 further displays back option 570 toenable the user to navigate back to the “Shared With You” user interfaceand an “edit” button 572 that, when selected, allows the user to editthe selected photo (e.g., using editing options, including one or more(or two or more, or a subset of) options to: crop, magnify, modifycolors, apply filters, straighten, and/or add annotations, to the mediaitem). In some embodiments, device 100 also displays a navigation bar574 that includes representations (e.g., thumbnails) of the media itemsdisplayed in the “All Photos” view. In some embodiments, navigation bar574 allows the user to navigate (e.g., by swiping along the navigationbar 574) between different media items (e.g., media items that areincluded in the media library and/or media items that are displayed inthe “Shared With You” user interface shown in FIG. 5P). In someembodiments, navigation bar 574 displays a representation of theselected (e.g., enlarged) photo (e.g., photo 517) that is larger, andoptionally displayed at a different magnification, than therepresentations of the other media items displayed in the navigation bar574.

In some embodiments, device 100 displays a first set of controls,including a share control 576 to allow the user to share (e.g., usingone or more communication applications) the enlarged media item, an Addto Library control 578 to allow the user to save (e.g., add) theenlarged media item to the media library of the user, and a deletecontrol 580 for removing (e.g., deleting) the enlarged media item fromthe set of photos available to be displayed in the photos application.

FIG. 5R illustrates receiving a first user input 582 (e.g., a tap input)on Add to Library control 578. In response to receiving first user input582, device 100 adds the selected media item to the user's media library(e.g., the media library of the photos application), and optionallydisplays the user interface illustrated in FIG. 5S. For example, device100 updates the first set of controls to replace Add to library control578, shown in FIG. 5R, with favorite control 586, shown in FIG. 5S. Forexample, because photo 517 has now been added to the media library ofthe user, device 100 ceases display of the Add to Library control. Insome embodiments, the sharing information 566 displayed in FIG. 5S isoptionally not displayed after the selected media item has been added tothe media library.

In some embodiments, as shown in FIG. 5S, device 100 detects user input588 (e.g., a tap input), and in response to user input 588, ceasesdisplay of all of the user interface elements (e.g., as illustrated inFIG. 5T) other than the enlarged photo 517. For example, device 100forgoes displaying navigation bar 574, the set of controls 576, 586, and580, back button 570 and edit button 572, and/or sharing information566. In some embodiments, a user input (e.g., a tap input) detected onthe enlarged photo toggles display of one or more of the user interfaceelements to be displayed or not. For example, in response to detecting auser input on enlarged photo 517 in FIG. 5T, the user interface elementsare redisplayed, as shown in FIG. 5S.

FIG. 5R further illustrates receiving a second user input 584 (e.g., atap input) on “Go to Messages” 568. In response to second user input584, device 100 displays the user interface illustrated in FIG. 5U. Forexample, device 100 opens messaging application and displays the messagethread in which the enlarged photo 517 was shared (e.g., the messagethread with Tom). In some embodiments, device 100 displays the portionof the message thread in which the media item was shared (e.g., message504-3). In some embodiments, device 100 displays a most recent portionof the message thread (e.g., that does not include the message in whichthe enlarged photo 517 was shared). In some embodiments, in response tosecond user input 584, device 100 displays a preview of the messagingapplication (e.g., without switching to the messaging application). Forexample, a portion, less than all, of the user interface illustrated inFIG. 5R is updated to display the message thread with Tom (e.g., insteadof opening the message thread in the messaging application).

In some embodiments, user input 588 is detected on an option to go Backto Photos from the messaging application, as illustrated in FIG. 5U. Inresponse to user input 588, device 100 displays the user interfaceillustrated in FIG. 5V (e.g., returns to the photos application, andoptionally displays the last user interface of the photos applicationthat was displayed prior to the device transitioning to displaying themessaging application).

In some embodiments, as illustrated in FIG. 5V, after photo 517 has beenadded to the user's library, device 100 ceases display of sharingindication 562 (e.g., shown in FIG. 5P). Accordingly, a user is able todistinguish between shared photos that have been added by the user tothe user's media library and shared photos that have not been added tothe user's media library (e.g., which the device continues to displaywith sharing indications, such as sharing indications on the corner ofthe photos).

In some embodiments, the “Shared With You” user interface illustrated inFIG. 5V includes an option to filter the displayed media items to onlydisplay unsaved media items, or to display all media items that wereshared (e.g., whether the respective media item has been added to theuser's library or not). For example, toggle switch 590 provides the userwith an option to select whether the photos that the device displays inthe “Shared With You” user interface includes “All Photos,” includingphoto 517 that has been saved to the media library of the user, orincludes only unsaved shared photos 527, 526, 563, etc. In someembodiments, device 100 receives user input 592 selecting to toggle todisplay unsaved photos in the “Shared With You” user interface withoutdisplaying shared content that has been added to the user's medialibrary. In response to user input 592, device 100 displays the userinterface illustrated in FIG. 5W, which displays unsaved shared mediaitems (e.g., photos 527, 526, 563,529, etc.) without displaying sharedcontent that has been saved to the user's media library (e.g., photo 517is not displayed in FIG. 5W). FIG. 5W further illustrates receiving userinput 594 on toggle switch 590 requesting to toggle back to displayingall photos, which is illustrated in FIG. 5X.

FIG. 5X illustrates receiving user input 595 (e.g., a tap input) onphoto 563. In some embodiments, in response to detecting user input 595,device 100 displays an enlarged representation of photo 563, asillustrated in FIG. 5Y. As noted above, in some embodiments, one or moremedia items (e.g., photo 563) are not displayed in the “All Photos” viewof the media library (e.g., as illustrated in FIG. 5K) based on displaycriteria (e.g., the one or more media items that are not displayed donot satisfy the display criteria). In some embodiments, the one or moremedia items that are not displayed in the “All Photos” view aredisplayed in the “Shared With You” user interface, which includes allmedia items (e.g., photos) that were shared with device 100 (e.g.,including shared media items that do not satisfy the display criteria).In some embodiments, navigation bar 574 is optionally not displayed forenlarged media items that do not appear in the “All Photos” view (e.g.,the navigation bar 574 allows a user to navigate between photos andshared photos displayed in the “All Photos” view, but photo 563 is notdisplayed in the “All Photos” view).

FIG. 5Y illustrates device 100 receiving user input 596 (e.g., a tapinput) on Add to Library control 578. In response to detecting userinput 596, device 100 adds (e.g., saves) photo 563 to the media libraryof the user, and updates the user interface to include controls enabledfor photos that are saved to the user's library, as illustrated in FIG.5Z. For example, FIG. 5Z illustrates navigation bar 574 and favoritecontrol 586, which are displayed concurrently with the enlargedrepresentation of photo 563.

FIG. 5Z further illustrates user input 598 selecting the back control.In response to user input 598, device 100 updates display of the userinterface to redisplay the “Shared With You” user interface illustratedin FIG. 5AA. FIG. 5AA further illustrates device 100 detecting userinput 5100 selecting the Library view. In response to user input 5100,device 100 displays the “All Photos” library view, as illustrated inFIG. 5AB.

FIG. 5AB illustrates that, after photo 517 is added to the medialibrary, photo 517 is optionally no longer displayed with a sharingindication (e.g., photo 517 is displayed without border 546). In someembodiments, after photo 563 is added to the media library, photo 563 isdisplayed in the “All Photos” view (e.g., as compared to the “AllPhotos” view illustrated in FIG. 5K, before photo 563 is added to themedia library). For example, the “All Photos” view of the libraryincludes one or more (e.g., all) of the photos that are saved in theuser's media library and one or more shared media items that meetdisplay criteria (e.g., and that have not been saved to the user'slibrary).

FIG. 5AC illustrates receiving user input 5102 requesting to return tothe “For You” view. In some embodiments, in response to user input 5102,device 100 displays the user interface in FIG. 5AD (e.g., in someembodiments, device 100 directly redisplays the “Shared With You”interface, and, in some embodiments, the user first navigates to the“Shared With You” interface from the “For You” interface as describedwith reference to FIGS. 5N-5P).

FIG. 5AD illustrates receiving user input 5104 (e.g., a tap input)selecting photo 526. In response to user input 5104, device 100 displaysan enlarged representation of photo 526 (e.g., which was shared by Bettyin “BFF Group” using the messaging application), as illustrated in FIG.5AE. FIG. 5AE further illustrates device 100 receiving user input 5106selecting the delete control. In response to selection of the deletecontrol, device 100 ceases to display the selected photo 526. Forexample, FIG. 5AF illustrates that photo 526 is no longer displayed inthe “Shared With You” interface (e.g., as compared to the interfaceillustrated in FIG. 5AD). In some embodiments, in response to deletingphoto 526 from the photos application, the message in the message threadthat includes shared photo 526 is optionally not deleted. For example,message 512-3 (FIG. 5I) is maintained in the message thread for “BFFGroup” on device 100 even after the user has deleted photo 526 fromdisplay within the photos application.

FIG. 5AF further illustrates detecting user input 5108 selecting photo527. In response to detecting user input 5108, device 100 displays anenlarged representation of photo 527 (e.g., and optionally displayssharing information 5109, including an indication of the user thatshared the photo (e.g., Betty), an application in which the photo wasshared (e.g., Messages), and a location of the photo (e.g., SanFrancisco)), as illustrated in FIG. 5AG. FIG. 5AG further illustratesuser input 5110 selecting “Go to Messages” button, which causes device100 to open messaging application (e.g., the message thread, “BFFGroup”, corresponding to where photo 527 was shared), as illustrated inFIG. 5AH.

FIG. 5AH further illustrates user input 5112 (e.g., a tap input)selecting the back button in the messaging application, which causesdevice 100 to display the plurality of message threads (e.g., asdescribed with reference to FIG. 5F). In some embodiments, asillustrated in FIG. 5AI, user input 5114 (e.g., a swipe input) isdetected on a portion of the user interface corresponding to arespective message thread. In response to user input 5114, device 100displays an option to delete 5116 the respective message thread, asillustrated in FIG. 5AJ. In some embodiments, device 100 provides anoption to select a plurality of message threads (e.g., two or more) tobe deleted at the same time (e.g., rather than requiring the user toperform a swipe input on each message thread). In some embodiments,device 100 provides an option to select one or more messages within amessage thread to delete (e.g., without deleting the entire messagethread).

FIG. 5AJ illustrates user input 5118 (e.g., a tap input) selecting theoption to delete 5116 the message thread corresponding to “BFF Group.”In response to user input 5118, the representation of the message threadfor BFF Group is removed from display of the plurality of messagethreads, as illustrated in FIG. 5AK. In some embodiments, in response todeleting a respective message thread, shared media items that wereshared via the respective message thread are deleted (e.g., no longerdisplayed in the “Shared With You” interface), as illustrated in FIG.5AM, described below.

FIG. 5AL illustrates user input 5120 selecting icon 428 corresponding tophotos application. In some embodiments, in response to user input 5120,device 100 opens the photos application and displays the “All Photos”view in FIG. 5AM. Because the “BFF Group” message thread was deleted(e.g., in the messaging application), the photos that were shared in BFFGroup (e.g., the shared photos that were not added to the media libraryby the user) are no longer displayed in the “All Photos” view. Forexample, FIG. 5AM illustrates the “All Photos” view without displayingshared media items that were shared in the BFF Group message thread(e.g., that is deleted from the messaging application). For example,comparing the photos illustrated in FIG. 5AM with the photos illustratedin FIG. 5AC (e.g., before deleting the BFF Group message thread), photos522, 526 and 527 are no longer displayed in FIG. 5AM.

In some embodiments, any photos shared in the BFF Group message threadthat were stored (e.g., saved) to the user's media library are notdeleted from the user's media library in accordance with the userdeleting the BFF Group message thread. For example, only unsaved sharedmedia items from a respective message thread are deleted in response tothe user deleting the respective message thread. In some embodiments orcircumstances, a user deletes one or more individual messages from amessage thread (e.g., without deleting the entire message thread). Inresponse, media items that are shared in the one or more individualmessages that are deleted are removed from the “All Photos” view,without removing media items that are shared in individual messages inthe message thread that have not been deleted.

FIG. 5AN illustrates user input 5120 selecting shared photo 528 from the“All Photos” view. In response to user input 512, device 100 displays anenlarged representation of photo 528, as illustrated in FIG. 5AO. FIG.5AO illustrates that photo 528 is shared by Zach using an emailapplication (e.g., a communication application distinct from themessaging application). It will be understood that various differentcommunication applications (or a combination of communicationapplications) may be used to share media items (e.g., Instant Messaging,Email, device-to-device network, etc.) and, in some embodiments, device100 displays information related to the application used to share therespective media item in response to the user selecting the media item(e.g., to view an enlarged representation of the media item). In someembodiments, additional sharing metadata is provided to (e.g., displayedfor) the user. For example, in response to a user input (e.g., a swipeup or down), device 100 displays additional metadata about the selectedmedia item (e.g., including sharing metadata), such as a time that theselected media item was captured (e.g., created), a location associatedwith the selected media item, individuals tagged (e.g., or recognized)in the selected media item, etc.

In some embodiments, a user is enabled to navigate between media items(e.g., including shared media items that have not been saved to themedia library of the user) using navigation bar 574. For example, asillustrated in FIG. 5AP, photo 528 has not been saved to the user'slibrary (e.g., and thus, device 100 continues to display a control to“Add to Library”). In response to user input 5120 (e.g., a swipe inputto the right) directed to navigation bar 574, device 100 replacesdisplay of the enlarged representation of photo 528 with display of anenlarged representation of photo 5124 (e.g., which is to the left of therepresentation of photo 528 in the navigation bar 574), as illustratedin FIG. 5AQ. In some embodiments, a user input that continues to move(e.g., swipe) to the right will cause device 100 to continue scrollingthrough media items in the navigation bar 574. In some embodiments, oneor more tactile outputs are provided as the user scrolls through themedia items.

FIGS. 6A-6P illustrate example user interfaces for performing a searchof media items in an application, including displaying search resultsthat include unsaved media items that are shared using a distinctapplication in accordance with some embodiments.

FIG. 6A illustrates device 100 displaying a “Shared With You” interfacein the photos application, as described above. Device 100 detects userinput 602 (e.g., a tap input), for example at a location correspondingto a search option, to navigate to the “Search” view in the photosapplication. In response to user input 602, device 100 displays a Searchuser interface, as illustrated in FIG. 6B.

For example, FIG. 6B illustrates a Search user interface, which includessearch bar 604 and a plurality of sections, including “People”, “Places”and “Categories”. In some embodiments, each section is automatically(e.g., without user input) curated with recommendations, includingrecommended people, places, or categories based on relevance criteria.For example, device 100 automatically displays people that appear mostoften in the user's photo library, the locations where the user (ordevice 100) is most often located, and categories for the user'sinterest (e.g., based on content of media items in the user's medialibrary).

FIG. 6C illustrates user input 606 (e.g., a swipe input up) that causesdevice 100 to scroll the Search user interface. In some embodiments, theSearch user interface further includes a “Group Sharing” section, asillustrated in FIG. 6D. FIG. 6D further illustrates user input 608(e.g., a swipe input down) that causes device 100 to scroll the Searchuser interface in the reverse direction. Accordingly, a user is able tonavigate to different portions of the Search user interface by usingswipe inputs to scroll up and down in the user interface. In someembodiments, the user is enabled to select an icon corresponding to arecommended person, place, category and/or group to initiate a search onthe respective icon.

For example, FIG. 6E illustrates user input 610 (e.g., a tap input)selecting icon 612 associated with Tom. In response to user input 610,device 100 performs a search of media items that are associated with“Tom.” For example, the search is based on search criteria related toTom (e.g., photos of Tom, photos shared by Tom, etc.).

In FIG. 6F, device 100 returns the search results in a search resultsuser interface. In some embodiments, the displayed search resultsinclude media items that are saved to the user's library and media itemsthat are not saved to the user's library (e.g., shared media items thathave not been saved to the user's library). In some embodiments,displaying the search results includes displaying a distinct section for“Photos of Tom” and a section for “Photos Shared by Tom.” In someembodiments, a respective media item is associated with both sections(e.g., a photo of Tom that is also shared by Tom, such as photo 517). Insome embodiments, the respective media item that is associated with bothsections is displayed in both sections. In some embodiments, therespective media item that is associated with both sections is onlydisplayed in one section (e.g., even though it is categorized by bothsections) to remove duplication of displaying the same media item inmultiple sections. In some embodiments, device 100 provides a set ofoptions to enable the user to filter the search results. For example,device 100 displays a first option (e.g., virtual button) 614 (“Photosof Tom”), a second option (e.g., virtual button) 616 (“Shared Photos”),and a third option (e.g., virtual button) 618 (“All Photos”). Forexample, in FIG. 6F, the third option/button 618 is highlighted,indicating that “All Photos” that match the search results (e.g., for“Tom”) are displayed.

In some embodiments, user input 620 (e.g., a tap input) selects thesecond option/button 616 to filter the search results, so that thedisplayed search results all correspond to “Shared Photos.” For example,in response to user input 620, device 100 updates display to the userinterface illustrated in FIG. 6G, where only the photos shared by Tom(e.g., and/or photos of Tom that are shared by another individual),including photo 517 and 520 are displayed. FIG. 6G further illustratesthat shared photos optionally are displayed with a sharing indication624. In some embodiments, only the shared photos that have not beensaved to the user's library (e.g., photo 520) are displayed with sharingindication 624, without displaying the sharing indication on sharedphotos that have already been saved to the user's library (e.g., photo517). In some embodiments, after a shared photo has been added to themedia library of the user, the shared photo is no longer considered ashared photo, and the photos that are added to the media library are notincluded in the filtered search results of “Shared Photos.” For example,in some embodiments, photo 517 (e.g., which was shared by Tom in themessaging application and was saved to the media library of the user ofdevice 100), is not displayed in the filtered search results of FIG. 6Gbecause it is no longer categorized as a shared photo.

On the other hand, in some embodiments, after a shared photo has beenadded to the media library, device 100 continues to categorize the photoas a shared photo (e.g., based on where the photo originated). In suchembodiments, even after the user adds photo 517 to the media library ofthe user, photo 517 continues to be categorized as a shared photo (e.g.,a shared photo that has been saved).

In some embodiments, user input 622 (e.g., a tap input) selects button614 to filter the search results to “Photos of Tom.” In response to userinput 622, device 100 updates the display to the user interfaceillustrated in FIG. 6H. In some embodiments, the search results thatmatch the search criteria, and that match the filter criteria indicatedby the user-selected filter option (e.g., option/button 616), include:photos that are photos of Tom (e.g., photos include an image of Tom, asdetermined automatically by facial recognition and/or determined bymanually tagging of the photo) that were shared by Tom or any otheruser, and photos of Tom in the media library that were captured bydevice 100 (e.g., photos that were not shared).

FIG. 6I illustrates an example of entering a search criteria in searchbox 604. For example, the user enters “#smile” into the search box. Inresponse to receiving the search criteria (e.g., and/or a request tosearch), device 100 performs a search based on the search criteria. Insome embodiments, the search criteria match a message thread (e.g., textin the search criteria matches text used in a message thread), anddevice 100 displays search results that includes one or more media itemsthat were shared in the message thread, as illustrated in FIG. 6J. Forexample, in FIGS. 5B-5C, Tom sent a message 504-2 that included “#smile”followed by message 504-3 (e.g., which includes photo 517). Accordingly,the search results include photo 517 that is associated with the message“#smile.” In some embodiments, photo 517 is optionally displayed withsharing indication 626 (e.g., whether or not photo 517 has been saved tothe user's library). It will be understood that in some embodiments, thesearch criteria match text in a message thread sent or received by theuser of device 100, and that the search results optionally include mediaitems shared by the user of device 100 and/or media items shared withthe user of device 100 (e.g., from another individual) in the messagethread that matches the search criteria.

FIG. 6K illustrates user input 628 (e.g., a tap input) selecting icon630 associated with one of the recommended “Places” (e.g., SanFrancisco). In response to user input 628, device 100 performs a searchof media items that are associated with the place “San Francisco.” Forexample, the search is based on search criteria related to San Francisco(e.g., photos taken in San Francisco).

Device 100 displays the search results for “San Francisco” in FIG. 6L.In some embodiments, an option (e.g., virtual button) 616 is provided tofilter the search results to display shared photos without displayingphotos that were captured using device 100 (e.g., photos in the medialibrary of the user). In some embodiments, device 100 providesadditional options, e.g., an option to filter the search results toinclude only unsaved media items (e.g., shared media items that have notbeen saved to the media library of the user). In FIG. 6L, the searchresults display shared photos and photos that were not shared (e.g., asindicated by the highlighted “All Photos” button 618). For example, inthe displayed search results, the shared photos include sharingindications that overlay the photos, while the photos that were notshared (e.g., photos that are stored in the media library of the user orphotos captured by device 100) are displayed without a sharingindication overlaid with the photo.

FIG. 6M illustrates user input 632 (e.g., a tap input) selecting icon634 associated with Alice. In response to user input 632, device 100performs a search of media items that are associated with “Alice.” Forexample, the search is based on search criteria related to Alice (e.g.,photos of Alice, photos shared by Alice, etc.).

Device 100 displays the search results, produced in response to userinput 632, in the user interface illustrated in FIG. 6N. In someembodiments, the displayed search results include media items that aresaved to the user's library and media items that are not saved to theuser's library (e.g., shared media items that have not been saved to theuser's library). In some embodiments, displaying the search resultsincludes displaying a separate section for “Shared Photos of Alice”(e.g., shared by Alice, or shared by someone other than Alice) and asecond for “Photos of Alice.” In some embodiments, a respective mediaitem is associated with both sections (e.g., a photo of Alice that isalso shared). In some embodiments, the respective media item that isassociated with both sections is displayed in both sections. In someembodiments, the respective media item that is associated with bothsections is only displayed in one section (e.g., even though it iscategorized by both sections) to remove duplication of displaying thesame media item in both sections. In some embodiments, device 100provides a set of options to enable the user to filter the searchresults (e.g., options to filter the search results to include only“Photos of Alice,” or only “Shared Photos,” or “All Photos”).

FIG. 6O illustrates another example of receiving search criteria insearch box 604. For example, FIG. 6O illustrates a request to search for“BFF Group.” In some embodiments, device 100 returns search results formedia items that were shared in a group message thread that isassociated with the identifier “BFF Group,” as shown in FIG. 6P. In theexample shown in FIGS. 6O-6P, the search was performed and the searchresults were produced before the “BFF Group” message thread was deleted(as described with reference to FIGS. 5AI-5AK. For example, in someembodiments, after the “BFF Group” message thread is deleted, inresponse to the same search for “BFF Group,” device 100 would display amessage indicating that no results are found (e.g., because the mediaitems that are shared in the BFF Group message are deleted in accordancewith the BFF Group message thread being deleted).

FIG. 6P illustrates search results that match the search criteria “BFFGroup” as entered in FIG. 6O. In some embodiments, only shared mediaitems that have not been deleted are displayed in the search results.For example, while photo 526 was shared in the BFF Group message thread(e.g., in message 512-3, shown in FIG. 5H), photo 526 was deleted (e.g.,as described with reference to FIG. 5AE). Accordingly, as shown in FIG.6P, photo 526 is not displayed in the search results of “BFF Group.”

FIGS. 7A-7E are flow diagrams illustrating method 700 of concurrentlydisplaying media items in an application with shared media items thatare received via a distinct application, in accordance with someembodiments. Method 700 is performed at a computer system (e.g., device300, FIG. 3 , or portable multifunction device 100, FIG. 1A) that is incommunication with a display generation component (e.g., a display) andone or more input devices. The computer system optionally includes(e.g., or is in communication with) a touch-sensitive surface, andoptionally includes one or more sensors to detect intensity of contactswith the touch-sensitive surface. In some embodiments, the displaygeneration component is a touch-screen display and the touch-sensitivesurface is on or integrated with the display generation component. Insome embodiments, the display generation component is separate from thetouch-sensitive surface. Some operations in method 700 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described herein, method 700 determines when a respective media itemhas been shared with the user using an application, and automaticallydisplays the respective media item in a media application withoutrequiring the user to provide inputs to select or add the media itemwithin the media application. In some embodiments, the methodautomatically displays the respective media item with a visual effect orvisual feature such that a user can distinguish between the respectivemedia item that was shared with the user and media items that arealready included in the user's media library of the media application.Performing an operation (e.g., automatically) when a set of conditionshas been met without requiring further user input enhances theoperability of the system and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended result andreducing user mistakes when operating/interacting with the system),which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The computer system receives (702), by a first application, a pluralityof shared media items. In some embodiments, the first application is acommunication application, such as a messaging application, a mail(e.g., email) application, or a social media application. In someembodiments, the plurality of shared media items comprises a pluralityof shared photos, shared videos, and/or shared audio clips. For example,as described with reference to FIGS. 5A-5I, a plurality of photos areshared with device 100 (e.g., a user of device 100) in a messagingapplication.

After receiving the plurality of shared media items, the computer systemreceives (704), via the one or more input devices, a request to displaya view of a media application (e.g., a media library application, suchas a photos application). For example, as illustrated in FIG. 5J, userinput 514 on icon 428 causes device 100 to open the photos application.The media application includes a media library that includes a firstplurality of media items, as illustrated in FIG. 5K. In someembodiments, the first plurality of media items are media items thathave been saved (e.g., locally) to the media library (e.g., photos 516,518, 519, 521, 523, 524, 525, 528, 530 and 531 as described withreference to FIG. 5K). In some embodiments, the plurality of sharedmedia items includes a set of one or more media items that have not beenadded to the media library (e.g., photos 517, 520, 522, 526, 527 and529, as described with reference to FIG. 5K). In some embodiments, theplurality of shared media items is not stored within a media library ofthe second application and/or the plurality of shared media items is notlocally saved by the computer system in the second application (e.g.,the photos application). In some embodiments, the plurality of sharedmedia items is stored within the first application but not the secondapplication (e.g., the second application references the firstapplication to enable the device 100 to display a respective sharedmedia item). For example, the shared media item is stored within themessaging application but is not stored within the photos application.

In response to receiving the request to display the view of the mediaapplication, the computer system displays (706), via the one or moredisplay generation components, a collection of media items in the mediaapplication that are selected based on first criteria, as described withreference to FIG. 5K. In some embodiments, the collection of media itemsinclude media items from a particular time, a particular place, and/or aparticular event. In some embodiments, the first criteria is recencycriteria and an order of the media items displayed in the collection ofmedia items is based on the times at which the displayed media itemswere captured (e.g., the most recent media items are displayed aboveless recent media items).

Displaying the collection of media items includes (708) displaying asecond plurality of media items selected from the media library based onthe first criteria. In some embodiments, the second plurality of mediaitems comprises a subset, less than all, of the first plurality of mediaitems that have been saved to the media library. In accordance with adetermination that a first shared media item from the set of one ormedia items that have not been added to the media library meets displaycriteria, the display criteria including the first criteria, the firstshared media item in the collection of media items is displayedconcurrently with the second plurality of media items, wherein the firstshared media item is visually distinguished from the second plurality ofmedia items based on a visual feature (e.g., or using, for example, avisual effect such as a blur effect, filter effect, or border) that isseparate from content of the media item. For example, the media itemsare visually distinguished from each other by applying a filter to theshared media item(s) without applying the filter to the media items thatare not shared media items. For example, as described in FIG. 5K,sharing indication 532 is displayed over shared media items. In someembodiments, the first criteria include a time criteria (e.g., a recencycriteria) such that the second plurality of media items are selectedfrom a particular time frame (e.g., the past week, the past month, thepast year, etc.). In some embodiments, the display criteria include thefirst criteria and additional criteria, such as an individual criteria(e.g., an individual who shared the media items, an individual whoappears in the media items). For example, as described with reference toFIGS. 5X-5AB, photo 563 does not satisfy display criteria and is notdisplayed in the “All Photos” view in FIG. 5K.

In some embodiments, displaying the collection of media items includes(710), in accordance with a determination that a second shared mediaitem from the set of one or media items that have not been added to themedia library meets the first criteria, displaying the second sharedmedia item in the collection of media items concurrently with the secondplurality of media items. In some embodiments, the second shared mediaitem is visually distinguished from the second plurality of media itemsbased on the visual feature that is separate from content of the mediaitem. In some embodiments, each shared media item (e.g., including thefirst shared media item and the second shared media items) that has notbeen added to the media library is displayed as visually distinguishedfrom the second plurality of media items based on the visual featurethat is separate from content of the media item (e.g., as illustrated inFIGS. 5K and 5L). For example, the shared media items that have not beenadded to the media library are displayed with a different visual effect(e.g., filter, shape, emphasis, etc.) than media items that are saved tothe media library. In some embodiments, only the shared media items thathave not been added to the media library are visually distinguished fromthe second plurality of media items and shared media items that havebeen added to the media library are not visually distinguished from thesecond plurality of media items (e.g., after photo 517 has been saved tothe media library, photo 517 is no longer displayed with the sharingindicator (e.g., or border), as illustrated in FIGS. 5V and 5AB). Forexample, after the shared items have been saved to the media library,the shared items that have been added to the media library are includedin the second plurality of media items.

Displaying shared media items with a different visual effect than themedia items that are already stored in the media library makes it easyfor the user to see which media items have been shared with the userand/or media items that have not yet been saved the user's medialibrary. Performing an operation (e.g., automatically) when a set ofconditions has been met without requiring further user input enhancesthe operability of the system and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended result andreducing user mistakes when operating/interacting with the system),which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, displaying the first shared media item that isvisually distinguished from the second plurality of media itemscomprises (712) displaying the first shared media item with changedappearance of at least a portion of a border region of the first sharedmedia item. For example, the shared media items that have not been addedto the media library are displayed with a visual effect (e.g., sharingindication or border) around the respective shared media items and theitems in the second plurality of media items are not displayed with theborder. For example, as illustrated in FIG. 5V, photo 517 has been savedto the media library and is displayed without a sharing indicatoroverlaying the corner of photo 517 (or a border), while photos 527, 526and 563 are each displayed with the sharing indicator overlaying thebottom left corner of those photos. In some embodiments, a size of thefirst shared media item is smaller than a size of a media item in thesecond plurality of media items (e.g., the first shared media item isdisplayed at a smaller size to fit within the border), as illustrated inFIGS. 5L and 5AB.

Displaying media items that have been shared with the user that have notyet been added to the media library of the user with a different borderor indicator without displaying the border or indicator on media itemsthat are in the user's media library makes it easy for the user to seewhich media items have been shared with the user and/or media items thathave not yet been saved the user's media library. Performing anoperation (e.g., automatically) when a set of conditions has been metwithout requiring further user input enhances the operability of thesystem and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended result and reducing usermistakes when operating/interacting with the system), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, displaying the first shared media item that isvisually distinguished from the second plurality of media itemscomprises (714) displaying the first shared media item with a contentobscuring effect (e.g., blurring or darkening) applied to at least aportion of the first shared media item. In some embodiments, the border(e.g., border 546, FIG. 5L) comprises a blurred (content obscuring)effect. For example, the first shared media item appears (e.g., at afirst size) to overlay a blurred copy of the first shared media item(e.g., at a second size that is larger than the first size), wherein theborder comprises the blurred copy of the first shared media item that isnot covered by the overlaid first shared media item.

Displaying media items that have been shared with the user that have notyet been added to the media library of the user with a blurred visualeffect without displaying the blurred visual effect on media items thatare in the user's media library makes it easy for the user to see whichmedia items have been shared with the user and/or media items that havenot yet been saved the user's media library. Performing an operation(e.g., automatically) when a set of conditions has been met withoutrequiring further user input enhances the operability of the system andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, displaying the first shared media item that isvisually distinguished from the second plurality of media itemscomprises (716) displaying the first shared media item with a graphicalelement that is overlaid on at least a portion of the first shared mediaitem. In some embodiments, the graphical element comprises an icon(e.g., an icon that corresponds to an application that was used to sharethe item with the user). For example, in FIG. 5K, the icon comprisessharing indication 532 on photo 520 to indicate photo 520 was shared viathe messaging application, and sharing indication 534 on photo 529indicates that photo 529 was shared via an email application. In someembodiments, the graphical element is at least partially translucent(e.g., the photo is visible under the graphical element).

Displaying media items that have been shared with the user that have notyet been added to the media library of the user with an overlaid iconwithout displaying the overlaid icon on media items that are in theuser's media library makes it easy for the user to see which media itemshave been shared with the user and/or media items that have not yet beensaved the user's media library. Performing an operation (e.g.,automatically) when a set of conditions has been met without requiringfurther user input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system receives (718) a sequence ofone or more user inputs including a user input selecting a media item inthe displayed collection of media items. In some embodiments, inresponse to receiving the sequence of one or more user inputs, thecomputer system displays (e.g., concurrently displays) an enlargedrepresentation of the media item and a plurality of controls forperforming operations associated with the media item. In someembodiments, in accordance with a determination that the media item is amedia item in the second plurality of media items selected from themedia library, the plurality of controls displayed (e.g., concurrentlydisplayed) with the enlarged representation of the media item include afirst set of controls. In some embodiments, in accordance with adetermination that the media item is a shared media item from the set ofone or more media items that have not been added to the media library,the plurality of controls displayed (e.g., concurrently displayed) withthe enlarged representation of the media item include a second set ofcontrols distinct from the first set of controls.

For example, media items that are already saved in the media library aredisplayed with the first set of controls, and media items that have notbeen added to the media library (e.g., shared media items) are displayedwith the second set of controls. In some embodiments, the second set ofcontrols includes controls that are also in the first set of controls.For example, the second set of controls includes a control to add themedia item to the media library and additional controls, and the firstset of controls includes the additional controls without the control toadd the media item to the media library. For example, as illustrated inFIG. 5R-5S, before photo 517 is added to the media library, theplurality of controls displayed with the enlarged representation ofphoto 517 includes an “Add to Library” control 578 (e.g., the second setof controls). After photo 517 has been added to the media library, theenlarged representation of photo 517 is displayed with a distinct set ofcontrols (e.g., the first set of controls), including a favorite control586. In some embodiments, the controls are displayed in response to theselection of the media item (e.g., the user input requesting to enlargethe media item). In some embodiments, the controls are displayed inresponse to a tap that is detected on the enlarged representation afterthe enlarged representation is displayed. In some embodiments, thecontrols are initially displayed and disappear in response to detectinga tap input on the enlarged representation of the media item while theplurality of controls are displayed. For example, as illustrated in FIG.5S-5T, in response to user input 588 (e.g., a tap input), device 100ceases to display controls 576, 586, and 580 concurrently with theenlarged photo 517.

Providing different sets of selectable controls based on whether a mediaitem has not been added to media library or the media item is alreadysaved to the media library provides real-time visual feedback to theuser and improves the user experience by allowing the user to performdifferent tasks based on the particular media item. Providing improvedvisual feedback to the user without requiring further user inputenhances the operability of the system and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result and reducing user mistakes when operating/interactingwith the system), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the first set of controls includes (720) a controlfor marking the media item as a favorite and/or a control for deletingthe media item. For example, favorite control 586 and/or delete control580, illustrated in FIG. 5S, are included in the first set of controls(e.g., displayed for media items saved to the media library). In someembodiments, in response to receiving an input on the control formarking the media item as a favorite, a favorite indicator (e.g., aheart) is displayed on the media item (e.g., the favorite control 586 isfilled in). In some embodiments, in response to receiving an input onthe control for deleting the media item, the media item is deleted fromthe collection of media items (and/or is deleted from the medialibrary), as described with reference to FIGS. 5AE-5AF. In someembodiments, in response to receiving an input on the control fordeleting the media item, the computer system ceases display of the mediaitem.

Providing a control for media items that allows a user to delete themedia content item such that the device no longer displays the mediacontent item provides additional control options without needing tonavigate through complex menu hierarchies and improves the userexperience. Providing improved visual feedback to the user, and (e.g.,automatically) providing additional control options when a set ofconditions has been met without cluttering the user interface withadditional displayed controls and without requiring further user inputenhances the operability of the system and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result and reducing user mistakes when operating/interactingwith the system), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the second set of controls includes (722) anindication that the selected media item is a shared media item. Forexample, the second set of controls that is displayed if the media itemis a shared media item that has not been added to the media libraryincludes an indication of an individual who shared the media item (e.g.,a contact name). For example, as illustrated in FIG. 5Q, sharinginformation 566 is displayed with the enlarged photo 517. In someembodiments, the indication that the selected media item is a sharedmedia item comprises visually distinguishing (e.g., adding a borderand/or a blur effect) the selected media item from the media items thatare in the second plurality of media items (selected from the medialibrary based on the first criteria). For example, in some embodiments,the border and/or graphical element is displayed on the enlarged mediaitem.

Automatically displaying an indication that a particular media item is amedia item that was shared with the user (e.g., from another user and/orvia another application) provides real-time visual feedback to the userand improves the user experience. Providing improved visual feedback tothe user, without requiring further user input, enhances the operabilityof the system and makes the user-device interface more efficient (e.g.,by helping the user to achieve an intended result and reducing usermistakes when operating/interacting with the system), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, while displaying the enlarged representation of themedia item and the plurality of controls for interacting with the mediaitem, the computer system receives (723) an input selecting the controlfor adding the media item to the media library. In some embodiments, inresponse to receiving the input selecting the control for adding themedia item to the media library, the computer system adds the media itemto the media library and ceases to display the indication that theselected media item is a shared media item. For example, as describedwith reference to FIG. 5S, in some embodiments, sharing information 566is no longer displayed after photo 517 has been added to the medialibrary.

Automatically updating the control options for a media item that theuser has requested to add to the media library (e.g., by changing thepreviously displayed set of control options for media items that are notin the media library to the set of control options displayed for mediaitems that were shared and are now saved to the media library) providesreal-time visual feedback to confirm that the user successfully addedthe media item to the user's media library (e.g., and is no longerprovided with the controls displayed for shared media items that are notsaved to the media library). Providing improved visual feedback to theuser, and (e.g., automatically) providing different control options whena set of conditions has been met without cluttering the user interfacewith additional displayed controls and without requiring further userinput enhances the operability of the system and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result and reducing user mistakes when operating/interactingwith the system), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the second set of controls includes (724) a controlfor adding the media item to the media library (e.g., as shown in FIG.5Q). In some embodiments, the second set of controls that is displayedif the media item is a shared media item that has not been added to themedia library includes an option to save the media item (e.g., locally)within the media application (e.g., “Add to Library” control 578).

Automatically providing a control for media items that have been sharedwith a user such that the user may add the media item to the user's ownmedia library provides additional control options without needing tonavigate through complex menu hierarchies and improves the userexperience. Providing improved visual feedback to the user, and (e.g.,automatically) providing additional control options when a set ofconditions has been met without cluttering the user interface withadditional displayed controls and without requiring further user inputenhances the operability of the system and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result and reducing user mistakes when operating/interactingwith the system), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, while displaying the enlarged representation of themedia item and the plurality of controls for interacting with the mediaitem, the computer system receives (726) an input selecting the controlfor adding the media item to the media library. In response to receivingthe input selecting the control for adding the media item to the medialibrary, and optionally, updates the set of controls that are displayed.For example, as shown in FIGS. 5R-5S, in some embodiments, in responseto receiving (726) the input selecting the control for adding the mediaitem to the media library, and in conjunction with adding the media itemto the media library, the computer system ceases (727) to display one ormore controls for performing operations associated with the media itemthat were displayed prior to receiving the input selecting the controlfor adding the media item to the media library. More specifically, insome embodiments, in response to receiving (726) the input selecting thecontrol for adding the media item to the media library, and inconjunction with adding the media item to the media library, thecomputer system ceases (728) to display the control (e.g., the “Add toLibrary” control 578 shown in FIG. 5R) for adding the media item to themedia library (e.g., which is one of the controls in the second set ofcontrols).

In yet another example, which is optionally combined with the either ofthe previous examples (727 or 728) of updates to the displayed set ofcontrols, in response to receiving (726) the input selecting the controlfor adding the media item to the media library, and in conjunction withadding the media item to the media library, the computer system displays(729) one or more controls (e.g., one or more controls from the firstset of controls, such as favorite control 586, FIG. 5S) for performingoperations associated with the media item in the media library that werenot displayed prior to receiving the input selecting the control foradding the media item to the media library (e.g., favorite control 586).

Automatically updating the control options for a media item that theuser has requested to add to the media library (e.g., by removing apreviously displayed control option to add the media item to the medialibrary, and/or by displaying a control only applicable to media itemsin the media library) provides real-time visual feedback to confirm thatthe user successfully added the media item to the user's media library(e.g., and is no longer provided with an option to add the media item tothe media library). Providing improved visual feedback to the user, and(e.g., automatically) providing different control options when a set ofconditions has been met without cluttering the user interface withadditional displayed controls and without requiring further user inputenhances the operability of the system and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result and reducing user mistakes when operating/interactingwith the system), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the computer system displays (732), concurrentlywith the enlarged representation of the media item, information about asource of the media item. For example, the information includesinformation about an application in which the media item was sharedand/or information about a user that shared the media item. For example,sharing information 566 is displayed concurrently with enlarged photo517, as described with reference to FIG. 5Q.

Displaying additional information related to a shared media item (e.g.,a person who shared the media item, a time that the media item wasshared, an identifier of an application used to share the media item)while also displaying the shared media item provides the user withreal-time visual feedback regarding how the media item was shared andprovides additional information to the user without needing to navigatethrough complex menu hierarchies. Providing improved visual feedback tothe user, and (e.g., automatically) providing additional control optionswhen a set of conditions has been met without cluttering the userinterface with additional displayed controls and without requiringfurther user input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, while concurrently displaying the enlargedrepresentation of the media item and the information about a source ofthe media item, the computer system detects (734) an input directed to aselectable user interface object that includes the information about thesource of the media item (e.g., user input 584, FIG. 5R). In someembodiments, in response to detecting an input directed to theselectable user interface object that includes the information about thesource of the media item, the computer system initiates a process fordisplaying, in the communication application, a communication historyfor a conversation in which the shared item was shared (e.g., asdescribed with reference to FIGS. 5R and 5U). For example, in responseto a user input selecting the option to view information about how themedia item was shared, the computer system automatically displays thecommunication application in which the media item was shared (e.g.,including displaying a portion of a communication thread within thecommunication application that includes when the media item was shared,or displaying a most recent portion of the communication thread withinthe communication application (even if the most recent portion of thecommunication thread does not include the shared media item)). In someembodiments, the input is a selection of the indication. In someembodiments, the input is a tap on a portion of a user interface thatpops up when you tap the indication (e.g., a first user input causes amenu to pop up in at least a portion of the user interface, the menuincluding an option to view information of how the media item wasshared, and a second user input selects the option to view theinformation of how the media item was shared). In some embodiments, theindication includes an identifier of the person who shared the mediaitem (e.g., sharing information 566 includes “Tom” and a representationof Tom (e.g., the circle with “T”)).

Providing a control option that is displayed for a shared media item toallow a user to navigate directly to a conversation in anotherapplication in which the media item was shared provides visual feedbackto the user that indicates a particular application and communicationhistory in which the media item was shared and provides additionalcontrol options to the user without needing to navigate through complexmenu hierarchies. Providing improved visual feedback to the user, and(e.g., automatically) providing additional control options withoutcluttering the user interface with additional displayed controls andwithout requiring further user input enhances the operability of thesystem and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended result and reducing usermistakes when operating/interacting with the system), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the media application includes (736) a plurality ofsections (e.g., wherein the plurality of sections includes a section fordisplaying the media library, a For You section, an Albums section,and/or a search section (e.g., as described with reference to FIG. 5K).In some embodiments, while displaying a first section of the pluralityof sections of the media application, the computer system automatically(e.g., without additional user input) displays the first shared mediaitem in the first section of the plurality of sections of the mediaapplication. For example, the plurality of sections includes a For Yousection (e.g., that is automatically generated and/or curated from mediaitems in the media library and/or shared media items not in the medialibrary). In some embodiments, the first section is the “For You”section, and the first section is divided into one or more subsections.In some embodiments, the one or more subsections includes a “Memories”subsection. In some embodiments, the one or more subsections includes a“Shared With You” section, a “Featured Photos” section, and/or a sectionof suggested media to be shared with others. In some embodiments, thefirst section is a “Memories” section (e.g., a highlights section). Insome embodiments, shared media item(s) are displayed in their ownsubsection (or section). For example, the “For You” section includes a“Shared With You” subsection that displays the plurality of shared mediaitem(s) that have been shared (e.g., whether they have been added to themedia library or not). For example, as described with reference to FIGS.5N-5O, a first shared media item 517 is displayed in the “For You”section (e.g., and within the “Memories” subsection 550).

Automatically displaying shared media items within a distinct section ofthe media application provides the user with real-time visual feedbackthat the media item is a shared media item without requiring the user tonavigate through complex menu hierarchies to obtain information about aparticular media item to determine if it is a shared media item.Providing improved visual feedback to the user without requiring furtheruser input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to a user input requesting to displaythe plurality of shared media items, the computer system displays (738)the set of one or more (shared) media items that have not been added tothe media library. In some embodiments, the user input requesting todisplay the plurality of shared media items is a user input selectingthe first section (or an option to expand the first section). Forexample, as described with reference to FIGS. 5N-5P, user input 560 on“See All” option 558 causes the device 100 to display “Shared With You”user interface. In some embodiments, the computer system only displaysunsaved shared photos (e.g., as described with reference to toggleswitch 590, FIGS. 5V-5X) without displaying shared photos that have beensaved to the media library (e.g., or photos that are not shared that aresaved in the media library).

Providing a control option that, when selected, displays all of theshared media items in a same user interface improves the user experienceby providing visual feedback that organizes the shared media items in adistinct user interface (e.g., or a distinct portion of the userinterface). Providing improved visual feedback to the user withoutrequiring further user input enhances the operability of the system andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the set of one or more (shared) media items thathave not been added to the media library that are displayed in responseto the user input requesting to display the plurality of shared mediaitems are displayed (740) without a visually distinguished appearance.For example, sharing indication 562 (e.g., shown in FIG. 5P) isoptionally not displayed on the shared media items in the “Shared WithYou” user interface.

Displaying shared media items, in response to a user input to speciallydisplay shared media items, without applying visual effects to thedisplayed shared media items avoids cluttering the user interface withsharing indicators that may not be useful to the user when all thedisplayed media items are shared media items, and avoids distracting theuser with information that may not be useful in the context ofdisplaying only shared media items. Performing an operation (e.g.,automatically) when a set of conditions has been met, and providingimproved visual feedback to the user, without requiring further userinput enhances the operability of the system and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result and reducing user mistakes when operating/interactingwith the system), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, in response to the user input requesting to displaythe plurality of shared media items, the computer system displays (742)the plurality of shared media items, including the set of the one ormore media items that have not been added to the media library and a setof one or more (shared) media items that have been added to the medialibrary. For example, as described with reference to FIG. 5X, photo 517has been added to the media library and device 100 continues to displayphoto 517 concurrently with photos 527, 526, and 563 that have not beenadded to the media library in the “Shared With You” user interface.

Providing a control option that, when selected, displays all of theshared media items concurrently, regardless of whether the shared mediaitem has already been saved to the media library, in a same userinterface improves the user experience by providing visual feedback thatallows the user to view all (e.g., or at least a subset, less than all)of the media items that were shared with the user, even after the userhas saved one or more of the shared media items to the media library.Providing improved visual feedback to the user without requiring furtheruser input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, media items in the set of the one or more mediaitems that have not been added to the media library are visuallydistinguished (744) from media items in the set of one or more mediaitems that have been added to the media library based on a visualfeature that is separate from content of the media items. For example,as illustrated in FIG. 5X, photo 517 (e.g., that has been added to themedia library) is displayed without a sharing indication, while photos527, 526, and 563 are displayed with a sharing indication (e.g., thegraphical element displayed in the bottom left corner of each photo).

Displaying shared media items that have not been saved to the medialibrary with a different visual effect than the shared media items thathave already been saved to the media library makes it easy for the userto see which media items have not yet been saved the user's medialibrary, which improves the visual feedback to the user such that theuser may easily select items to be saved to the media library.Performing an operation (e.g., automatically) when a set of conditionshas been met, and providing improved visual feedback to the user,without requiring further user input enhances the operability of thesystem and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended result and reducing usermistakes when operating/interacting with the system), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the display criteria include (746) relevancecriteria. For example, in some embodiments, the relevance criteria isbased on a plurality of factors, such as two or more of: an age of themedia item (e.g., recency criteria indicating how recently the mediaitem was captured and/or shared), location criteria, and a useridentification criteria. For example, as described with reference toFIGS. 5X-5AB, photo 563 in not initially displayed in the “All Photos”view (e.g., of FIG. 5K), because photo 563 does not meet relevancecriteria.

Automatically selecting a set of media items that satisfy relevancecriteria improves the user experience and provides improved visualfeedback to the user by displaying, for the user, only those media itemsthat are likely to be relevant the user. Performing an operation (e.g.,automatically) when a set of conditions has been met, and providingimproved visual feedback to the user, without requiring further userinput enhances the operability of the system and makes the user-deviceinterface more efficient (e.g., by helping the user to achieve anintended result and reducing user mistakes when operating/interactingwith the system), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the display criteria include (748) locationcriteria indicating that a user of the computer system was located at asame location corresponding to the shared media item. For example, thelocation criteria is based on whether the user was at the same location(e.g., at the same time, or within a predetermined time window) at whichthe media item was captured. For example, the location criteria may bebased on device location data for a device associated with the user orbased on whether the user has photos in their photo library from thatlocation. In some embodiments, a predetermined time window (e.g., 1hour, 2 hours, 1 day, etc.) is used to compare when the photo was takenas compared to the location of the user (or a device associated with theuser) to determine whether there is overlap (e.g., that the user was atthe location). For example, as illustrated in FIG. 5Y, photo 563 wastaken in “London, England” and thus does not meet display criteria(e.g., wherein the user of the device (e.g., at the time the photo wastaken) is located at a different location (e.g., in California)).

Automatically selecting a set of media items that satisfy locationcriteria improves the user experience and provides improved visualfeedback to the user by displaying, for the user, only those media itemsthat were taken or shared at a location that is associated with the user(e.g., because the user was at the location). Performing an operation(e.g., automatically) when a set of conditions has been met, andproviding improved visual feedback to the user, without requiringfurther user input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently

In some embodiments, the display criteria include (750) useridentification criteria that indicates if a user of the computer systemappears in the media item. For example, the user identification criteriaindicates whether the user (e.g., the user of device 100) is captured inthe media item (e.g., if the user is in the photo). In some embodiments,the display criteria include identification criteria that indicates if aparticular person (e.g., a contact, such as Tom) or other identifiedbeing (e.g., a pet) is detected (e.g., appears) in the media item and/orin your photo library (e.g., a pet that is in your photo library isdetected in the photo).

Automatically selecting a set of media items that satisfy criteria basedon the user appearing within the media item improves the user experienceand provides improved visual feedback to the user by displaying, for theuser, only those media items that include the user within the mediaitem. Performing an operation (e.g., automatically) when a set ofconditions has been met, and providing improved visual feedback to theuser, without requiring further user input enhances the operability ofthe system and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended result and reducing usermistakes when operating/interacting with the system), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system receives (752), by the firstapplication, a request to delete a communication thread in which thefirst media item that has not been added to the media library wasshared. In some embodiments, in response to receiving the request todelete the communication thread, the computer system forgoes displayingthe first shared media item in the collection of media items (e.g.,deleting the first shared media item from the collection of media items)when the collection of media items is displayed. For example, asdescribed with reference to FIGS. 5AI-5AM, in response to deleting “BFFGroup” message thread in the messaging application, the photos shared in“BFF Group” message thread are no longer displayed in the photosapplication. For example, in response to a request to display theportion of the collection of media items with which the first media itemwas displayed, the portion of the collection of media items with whichthe first media item was displayed is displayed without displaying arepresentation of the first media item. In some embodiments, if thefirst media item was already saved (e.g., added) to the media library,deleting the communication thread does not delete the first media itemfrom the media library. For example, only unsaved shared media items aredeleted from the collection of media items in response to deleting thecommunication thread in which the media item was shared.

Automatically deleting a media item that was shared via a communicationthread in response to the communication thread being deleted improvesthe user experience and provides improved visual feedback to the user byno longer displaying the shared media item after the communicationthread has been deleted, thereby indicating that the thread and themedia item are no longer available to save to the media library.Additionally, automatically deleting the media item reduces the numberof inputs required by the user by automatically removing the media itemfrom display in the media application as well as from the communicationapplication in response to deleting the communication thread that sharedthe media item within the communication application. Performing anoperation (e.g., automatically) when a set of conditions has been met,and providing improved visual feedback to the user, without requiringfurther user input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently

In some embodiments, the display criteria include (754) recency criteriato display media items that have been shared within a predeterminedthreshold amount of time. For example, the set of one or media itemsthat have not been added to the media library meets display criteria inaccordance with a determination that the set of one or more media itemshave been shared within the last 30 days (e.g., or within the last year,month, or other time period). In some embodiments, the predeterminedthreshold amount of time is based on a user-defined setting. Forexample, a user who agrees to use a photo sharing feature extends thepredetermined threshold amount of time from 30 days to a year (orlonger). In some embodiments, the predetermined threshold amount of timeis measured from the date/time at which the user enabled a media sharingoption.

Automatically including shared media items in the media application thatwere shared within a predetermined preceding time period withoutrequiring the user to select or save the shared media items to bedisplayed in the media application improves the user experience andprovides improved visual feedback to the user by automatically updatingthe media application to display shared media items. Performing anoperation (e.g., automatically) when a set of conditions has been met,and providing improved visual feedback to the user, without requiringfurther user input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 7A-7E have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 800) are also applicable in an analogous manner to method 700described above with respect to FIGS. 7A-7E. For example, the userinterface objects described above with reference to method 700optionally have one or more of the characteristics of the user interfaceobjects described herein with reference to other methods describedherein (e.g., method 800). For brevity, these details are not repeatedhere.

FIGS. 8A-8B are flow diagrams illustrating method 800 of displayingsearch results for media items in an application, including concurrentlydisplaying media items saved in the application with shared media itemsthat are received via a distinct application in accordance with someembodiments. Method 800 is performed at a computer system (e.g., device300, FIG. 3 , or portable multifunction device 100, FIG. 1A) that is incommunication with a display generation component (e.g., a display) andone or more input devices. The computer system optionally includes(e.g., or is in communication with) a touch-sensitive surface, andoptionally includes one or more sensors to detect intensity of contactswith the touch-sensitive surface. In some embodiments, the displaygeneration component is a touch-screen display and the touch-sensitivesurface is on or integrated with the display generation component. Insome embodiments, the display generation component is separate from thetouch-sensitive surface. Some operations in method 800 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described herein, method 800 searches a media library to displaymedia items that meet search criteria, including automaticallydisplaying, in the search results, media items that are stored withinthe media library and media items that have been shared with the userbut are not stored within the media library. Performing an operation(e.g., automatically) when a set of conditions has been met withoutrequiring further user input enhances the operability of the system andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

The computer system receives (802), by a first application (e.g., acommunication application such as a messaging application, a mailapplication, or a social media application), a plurality of shared mediaitems. For example, as described with reference to FIGS. 5A-5I, theplurality of shared media items includes shared photos (e.g., receivedvia a messaging application).

After receiving the plurality of shared media items, the computer systemreceives (804), via the one or more input devices, a request to search amedia library of a second application that is different from the firstapplication for media items in the media library that meet searchcriteria. In some embodiments, the request defines the search criteria;wherein the search criteria comprises one or more features of the mediaitem, including: a person in the media item, a person who shared themedia item, a place, an object in the media item. For example, in FIG.6E, user input 610 requests to search for “Tom.” For example, in someembodiments, the search criteria comprises a place (e.g., location), asdescribed with reference to FIGS. 6K-6L.

In response to receiving the request to search the media library, thecomputer system concurrently displays (806), via the one or more displaygeneration components, two or more media items that meet the searchcriteria. For example, as illustrated in FIG. 6F, the search resultsmatching the user request (e.g., user input 610) to search for “Tom” isdisplayed.

The two or more media items include (808): one or more media items fromthe media library of the second application that meet the searchcriteria, and one or more of the shared media items that are not storedwithin the media library of the second application and that meet thesearch criteria. In some embodiments, the media items that are storedwithin the media library of the first application and the shared mediaitems are displayed concurrently (e.g., as search results, displayed inresponse to the search request). For example, as illustrated in FIG. 6F,the search results include at least two sections, “Photos of Tom” whichincludes photo 531 (e.g., which is stored in the media library and isnot a shared media item) and “Photos Shared by Tom” which includes photo520 (e.g., which is a shared media item that is not stored in the medialibrary). In some embodiments, a shared media item in the displayedsearch results is not stored within a media library of a secondapplication (e.g., the photos application) and/or is not locally savedby the computer system in the second application.

In some embodiments, the request to search the media library comprises(810) a request to search for an individual (e.g., a request to searchfor “Tom”) and the two or more media items include at least one mediaitem including the individual and at least one media item shared by theindividual, as illustrated in FIG. 6F. For example, the search resultsinclude photos shared by Tom in a message conversation with Tom, asdescribed with reference to FIGS. 5A through 5D-1 .

Automatically selecting a set of media items that satisfy searchcriteria based on the user, or other specified individual, appearingwithin the media item improves the user experience and provides improvedvisual feedback to the user by displaying within search results, for theuser, only those media items that include the user, or other specifiedindividual, within each of the media items. Performing an operation(e.g., automatically) when a set of conditions has been met, andproviding improved visual feedback to the user, without requiringfurther user input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the search criteria are satisfied (812) by amessage conversation and the two or more media items include one or moremedia items that have been shared in the message conversation. Forexample, the search may be satisfied by all or any messages in themessage conversation, one or more participants in the messageconversation, and/or a name/title/subject of the message conversation.In some embodiments, in accordance with a determination that a messageconversation satisfies the search criteria, the computer system selectsthe entire communication thread for purposes of determining what sharedmedia items to display in the search results (e.g., including mediaitems shared by a user of the computer system and/or media items sharedwith (e.g., from another person) the user of the computer system). Forexample, as described with reference to FIGS. 6I-6J, a user requests tosearch for “#smile” and the message thread with Tom matches the searchcriteria (e.g., because “#smile” appears in the messages with Tom), sodevice 100 displays at least one search result (e.g., photo 517) thatwas shared in the messages with Tom.

Automatically selecting a set of media items that satisfy searchcriteria based on the whether a media item had been shared within aparticular conversation improves the user experience and providesimproved visual feedback to the user by displaying within searchresults, for the user, only those media items that satisfy the searchcriteria, and enables the user to easily navigate to media items thatwere shared in the conversation that satisfies the search criteria.Performing an operation (e.g., automatically) when a set of conditionshas been met, and providing improved visual feedback to the user,without requiring further user input enhances the operability of thesystem and makes the user-device interface more efficient (e.g., byhelping the user to achieve an intended result and reducing usermistakes when operating/interacting with the system), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system displays (814) a firstuser-selectable option that, when selected, filters the concurrentlydisplayed two or more media items to only display one or more of theplurality of shared media items that were shared by a firstuser-specified individual. In some embodiments, in response to detectingselection of the first user-selectable option, the computer systemdisplays the one or more of the plurality of shared media items thatwere shared by the first user-specified individual without displayingother media items associated with the first user-specified individual(e.g., without displaying one or more media items that include theindividual within the media item, but were not shared by individual). Insome embodiments, the search criteria includes an identifier of anindividual and the first user-selectable option further filters theresults to only display the shared media items that were received from(e.g., shared by) the individual when the first user-selectable optionis selected. For example, as described with reference to FIGS. 6F-6H,the user is able to filter the search results using buttons 614, 616 and618 to cause the device to switch between display of Photos of Tom,Photos Shared by Tom, or both.

Providing a control option that allows a user to filter search resultsaccording to media items that were shared by a particular individualprovides improved visual feedback to the user that indicates which mediaitems, within the search results, were shared by the particularindividual versus media items that are otherwise associated with theparticular individual and provides additional control options to theuser without needing to navigate through complex menu hierarchies.Providing improved visual feedback to the user, and (e.g.,automatically) providing additional control options without clutteringthe user interface with additional displayed controls and withoutrequiring further user input enhances the operability of the system andmakes the user-device interface more efficient (e.g., by helping theuser to achieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the computer system displays (816) a seconduser-selectable option that, when selected, filters the concurrentlydisplayed two or more media items to display one or more media itemsthat include a second user-specified individual within the media item.In some embodiments, in response to detecting selection of the seconduser-selectable option, the computer system displays one or more mediaitems that include the second user-specified individual within the mediaitem without displaying other media items associated with the seconduser-specified individual (e.g., without displaying media items thatwere shared by the individual, but that do not include the individualwithin the media items). For example, as described with reference toFIGS. 6F-6H, the user is able to filter the search results using buttons614, 616 and 618 to cause the device to switch between display of Photosof Tom, Photos Shared by Tom, or both.

Providing a control option that allows a user to filter search resultsaccording to media items that include a particular individual within themedia item provides improved visual feedback to the user by only showingmedia items that include the particular individual without displayingmedia items that are otherwise associated with the particular individualbut do not include the particular individual within the media item, andprovides additional control options to the user without needing tonavigate through complex menu hierarchies. Providing improved visualfeedback to the user, and (e.g., automatically) providing additionalcontrol options without cluttering the user interface with additionaldisplayed controls and without requiring further user input enhances theoperability of the system and makes the user-device interface moreefficient (e.g., by helping the user to achieve an intended result andreducing user mistakes when operating/interacting with the system),which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the computer system displays (818) a thirduser-selectable option that, when selected, filters the concurrentlydisplayed two or more media items to display one or more of theplurality of shared media items that were shared within one or moregroups that include a third user-specified individual. In someembodiments, in response to detecting selection of the thirduser-selectable option, the computer system displays one or more of theplurality of shared media items that were shared by one or more groups(e.g., in a group communication thread) that include the thirduser-specified individual. For example, as illustrated in FIG. 6D, a“Group Sharing” portion of the Search user interface is provided. Insome embodiments, the “Group Sharing” portion of the Search userinterface includes representations of one or more groups that haveshared media items (e.g., BFF Group, Family Group). In some embodiments,in response to a user selecting a group of the one or more groups, thecomputer system displays search results that include media items sharedin the selected group. In some embodiments, the user provides anidentifier of a group as search criteria, as described with reference toFIGS. 6O-6P. In some embodiments, the first user-selectable option, thesecond user-selectable option, and/or the third user-selectable optionare concurrently displayed (e.g., the user can filter the search resultsusing any of the user-selectable options). In some embodiments, one ormore of the user-selectable options may be selected concurrently suchthat the user can filter the search results to display any combinationof (i) the one or more of the plurality of shared media items that wereshared by the first user-specified individual (ii) one or more mediaitems that include the second user-specified individual within the mediaitem and (iii) one or more of the plurality of shared media items thatwere shared by one or more groups that include the third user-specifiedindividual. In some embodiments, the first, second and thirduser-specified individual are the same individual. In some embodiments,the first, second, and/or third user-selectable options are displayedconcurrently with the search results. In some embodiments, the first,second, and/or third user-selectable options are displayed in responseto receiving the search input (e.g., and a request to search).

Providing a control option that allows a user to filter search resultsaccording to media items that were shared in a group communication,where the group includes a particular individual, provides improvedvisual feedback to the user by only showing media items that were sharedby the group, and provides additional control options to the userwithout needing to navigate through complex menu hierarchies. Providingimproved visual feedback to the user, and (e.g., automatically)providing additional control options without cluttering the userinterface with additional displayed controls and without requiringfurther user input enhances the operability of the system and makes theuser-device interface more efficient (e.g., by helping the user toachieve an intended result and reducing user mistakes whenoperating/interacting with the system), which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

It should be understood that the particular order in which theoperations in FIGS. 8A-8B have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 700) are also applicable in an analogous manner to method 800described above with respect to FIGS. 8A-8B. For example, the userinterface objects described above with reference to method 700optionally have one or more of the characteristics of the user interfaceobjects described herein with reference to other methods describedherein (e.g., method 700). For brevity, these details are not repeatedhere.

The operations described above with reference to FIGS. 7A-7E and 8A-8Bare, optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, receiving operation 704, displaying operation 708, receivingoperation 802, and displaying operation 806 are, optionally, implementedby event sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface (or whether rotation of thedevice) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method, comprising: at a computer system thatis in communication with a display generation component and one or moreinput devices: receiving, by a first application, a plurality of sharedmedia items; after receiving the plurality of shared media items,receiving, via the one or more input devices, a request to display aview of a media application wherein the media application includes amedia library that includes a first plurality of media items, and theplurality of shared media items includes a set of one or more mediaitems that have not been added to the media library; and in response toreceiving the request to display the view of the media application,displaying, via the display generation component, a collection of mediaitems in the media application that are selected based on firstcriteria, wherein displaying the collection of media items includes:displaying a second plurality of media items selected from the medialibrary based on the first criteria; and in accordance with adetermination that a first shared media item from the set of one or moremedia items that have not been added to the media library meets displaycriteria, the display criteria including the first criteria, displayingthe first shared media item in the collection of media itemsconcurrently with the second plurality of media items, wherein the firstshared media item is visually distinguished from the second plurality ofmedia items based on a visual feature that is separate from content ofthe first shared media item.
 2. The method of claim 1, whereindisplaying the collection of media items includes, in accordance with adetermination that a second shared media item from the set of one ormedia items that have not been added to the media library meets thefirst criteria, displaying the second shared media item in thecollection of media items concurrently with the second plurality ofmedia items, wherein the second shared media item is visuallydistinguished from the second plurality of media items based on thevisual feature that is separate from content of the second shared mediaitem.
 3. The method of claim 1, wherein displaying the first sharedmedia item that is visually distinguished from the second plurality ofmedia items comprises displaying the first shared media item withchanged appearance of at least a portion of a border region of the firstshared media item.
 4. The method of claim 1, wherein displaying thefirst shared media item that is visually distinguished from the secondplurality of media items comprises displaying the first shared mediaitem with a content obscuring effect applied to at least a portion ofthe first shared media item.
 5. The method of claim 1, whereindisplaying the first shared media item that is visually distinguishedfrom the second plurality of media items comprises displaying the firstshared media item with a graphical element that is overlaid on at leasta portion of the first shared media item.
 6. The method of claim 1,further comprising, receiving a sequence of one or more user inputsincluding a user input selecting a media item in the displayedcollection of media items; and in response to receiving the sequence ofone or more user inputs, displaying an enlarged representation of theselected media item and a plurality of controls for performingoperations associated with the selected media item, wherein: inaccordance with a determination that the selected media item is a mediaitem in the second plurality of media items selected from the medialibrary, the plurality of controls displayed with the enlargedrepresentation of the selected media item include a first set ofcontrols; and in accordance with a determination that the selected mediaitem is a shared media item from the set of one or more media items thathave not been added to the media library, the plurality of controlsdisplayed with the enlarged representation of the selected media iteminclude a second set of controls distinct from the first set ofcontrols.
 7. The method of claim 6, wherein the first set of controlsincludes a control for marking the selected media item as a favoriteand/or a control for deleting the selected media item.
 8. The method ofclaim 6, wherein the second set of controls includes an indication thatthe selected media item is a shared media item.
 9. The method of claim6, wherein the second set of controls includes a control for adding theselected media item to the media library.
 10. The method of claim 9,further comprising: while displaying the enlarged representation of theselected media item and the plurality of controls for interacting withthe selected media item, receiving an input selecting the control foradding the selected media item to the media library; and in response toreceiving the input selecting the control for adding the selected mediaitem to the media library: adding the selected media item to the medialibrary.
 11. The method of claim 10, including, in response to receivingthe input selecting the control for adding the selected media item tothe media library, ceasing to display one or more controls forperforming operations associated with the selected media item that weredisplayed prior to receiving the input selecting the control for addingthe selected media item to the media library.
 12. The method of claim10, including, in response to receiving the input selecting the controlfor adding the selected media item to the media library, ceasing displayof the control for adding the selected media item to the media library.13. The method of claim 10, including, in response to receiving theinput selecting the control for adding the selected media item to themedia library, displaying one or more controls for performing operationsassociated with the selected media item in the media library that werenot displayed prior to receiving the input selecting the control foradding the selected media item to the media library.
 14. The method ofclaim 6, including displaying, concurrently with the enlargedrepresentation of the selected media item, information about a source ofthe selected media item.
 15. The method of claim 14, including: whileconcurrently displaying the enlarged representation of the selectedmedia item and the information about a source of the selected mediaitem, detecting an input directed to a selectable user interface objectthat includes the information about the source of the selected mediaitem; and in response to detecting an input directed to the selectableuser interface object that includes the information about the source ofthe selected media item, initiating a process for displaying, in thefirst application, a communication history for a conversation in whichthe selected media item was shared.
 16. The method of claim 1, wherein:the media application includes a plurality of sections; and the methodfurther comprises, while displaying a first section of the plurality ofsections of the media application, automatically displaying the firstshared media item in the first section of the plurality of sections ofthe media application.
 17. The method of claim 1, further comprising, inresponse to a user input requesting to display the plurality of sharedmedia items, displaying the set of one or more media items that have notbeen added to the media library.
 18. The method of claim 17, wherein theset of one or more media items that have not been added to the medialibrary that are displayed in response to the user input requesting todisplay the plurality of shared media items, are displayed without avisually distinguished appearance.
 19. The method of claim 17, furthercomprising, in response to the user input requesting to display theplurality of shared media items, displaying the plurality of sharedmedia items, including the set of the one or more media items that havenot been added to the media library and a set of one or more media itemsthat have been added to the media library.
 20. The method of claim 19,wherein media items in the set of the one or more media items that havenot been added to the media library are visually distinguished frommedia items in the set of one or more media items that have been addedto the media library based on a visual feature that is separate fromcontent of the media items.
 21. The method of claim 1, wherein thedisplay criteria include one or more of the criteria selected from thegroup consisting of relevance criteria, location criteria indicatingthat a user of the computer system was located at a same locationcorresponding to the first shared media item, user identificationcriteria that indicates if a user of the computer system appears in thefirst shared media item, and recency criteria to display media itemsthat have been shared within a predetermined threshold amount of time.22. The method of claim 1, further comprising: receiving, by the firstapplication, a request to delete a communication thread in which thefirst shared media item that has not been added to the media library wasshared; and in response to receiving the request to delete thecommunication thread, forgoing display of the first shared media item inthe collection of media items when the collection of media items isdisplayed.
 23. A computer system, comprising: a display generationcomponent; one or more input devices; one or more processors; and memorystoring one or more programs, wherein the one or more programs areconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving, by a first application,a plurality of shared media items; after receiving the plurality ofshared media items, receiving, via the one or more input devices, arequest to display a view of a media application wherein the mediaapplication includes a media library that includes a first plurality ofmedia items, and the plurality of shared media items includes a set ofone or more media items that have not been added to the media library;and in response to receiving the request to display the view of themedia application, displaying, via the display generation component, acollection of media items in the media application that are selectedbased on first criteria, wherein displaying the collection of mediaitems includes: displaying a second plurality of media items selectedfrom the media library based on the first criteria; and in accordancewith a determination that a first shared media item from the set of oneor more media items that have not been added to the media library meetsdisplay criteria, the display criteria including the first criteria,displaying the first shared media item in the collection of media itemsconcurrently with the second plurality of media items, wherein the firstshared media item is visually distinguished from the second plurality ofmedia items based on a visual feature that is separate from content ofthe first shared media item.
 24. A non-transitory computer readablestorage medium storing one or more programs, the one or more programscomprising instructions, which, when executed by a computer system witha display generation component and one or more input devices, cause thecomputer system to: receive by a first application, a plurality ofshared media items; after receiving the plurality of shared media items,receive, via the one or more input devices, a request to display a viewof a media application wherein the media application includes a medialibrary that includes a first plurality of media items, and theplurality of shared media items includes a set of one or more mediaitems that have not been added to the media library; and in response toreceiving the request to display the view of the media application,display, via the display generation component, a collection of mediaitems in the media application that are selected based on firstcriteria, wherein displaying the collection of media items includes:displaying a second plurality of media items selected from the medialibrary based on the first criteria; and in accordance with adetermination that a first shared media item from the set of one or moremedia items that have not been added to the media library meets displaycriteria, the display criteria including the first criteria, displayingthe first shared media item in the collection of media itemsconcurrently with the second plurality of media items, wherein the firstshared media item is visually distinguished from the second plurality ofmedia items based on a visual feature that is separate from content ofthe first shared media item.
 25. The computer system of claim 23,wherein displaying the collection of media items includes, in accordancewith a determination that a second shared media item from the set of oneor media items that have not been added to the media library meets thefirst criteria, displaying the second shared media item in thecollection of media items concurrently with the second plurality ofmedia items, wherein the second shared media item is visuallydistinguished from the second plurality of media items based on thevisual feature that is separate from content of the second shared mediaitem.
 26. The computer system of claim 23, wherein displaying the firstshared media item that is visually distinguished from the secondplurality of media items comprises displaying the first shared mediaitem with changed appearance of at least a portion of a border region ofthe first shared media item.
 27. The computer system of claim 23,wherein displaying the first shared media item that is visuallydistinguished from the second plurality of media items comprisesdisplaying the first shared media item with a content obscuring effectapplied to at least a portion of the first shared media item.
 28. Thecomputer system of claim 23, wherein displaying the first shared mediaitem that is visually distinguished from the second plurality of mediaitems comprises displaying the first shared media item with a graphicalelement that is overlaid on at least a portion of the first shared mediaitem.
 29. The computer system of claim 23, wherein the one or moreprograms include instructions for: receiving a sequence of one or moreuser inputs including a user input selecting a media item in thedisplayed collection of media items; and in response to receiving thesequence of one or more user inputs, displaying an enlargedrepresentation of the selected media item and a plurality of controlsfor performing operations associated with the selected media item,wherein: in accordance with a determination that the selected media itemis a media item in the second plurality of media items selected from themedia library, the plurality of controls displayed with the enlargedrepresentation of the selected media item include a first set ofcontrols; and in accordance with a determination that the selected mediaitem is a shared media item from the set of one or more media items thathave not been added to the media library, the plurality of controlsdisplayed with the enlarged representation of the selected media iteminclude a second set of controls distinct from the first set ofcontrols.
 30. The computer system of claim 29, wherein the second set ofcontrols includes an indication that the selected media item is a sharedmedia item.
 31. The computer system of claim 29, wherein the second setof controls includes a control for adding the selected media item to themedia library.
 32. The computer system of claim 31, wherein the one ormore programs include instructions for: while displaying the enlargedrepresentation of the selected media item and the plurality of controlsfor interacting with the selected media item, receiving an inputselecting the control for adding the selected media item to the medialibrary; and in response to receiving the input selecting the controlfor adding the selected media item to the media library: adding theselected media item to the media library.
 33. The computer system ofclaim 32, wherein the one or more programs include instructions for: inresponse to receiving the input selecting the control for adding theselected media item to the media library, ceasing to display one or morecontrols for performing operations associated with the selected mediaitem that were displayed prior to receiving the input selecting thecontrol for adding the selected media item to the media library.
 34. Thecomputer system of claim 32, wherein the one or more programs includeinstructions for: in response to receiving the input selecting thecontrol for adding the selected media item to the media library,displaying one or more controls for performing operations associatedwith the selected media item in the media library that were notdisplayed prior to receiving the input selecting the control for addingthe selected media item to the media library.
 35. The computer system ofclaim 29, wherein the one or more programs include instructions fordisplaying, concurrently with the enlarged representation of theselected media item, information about a source of the selected mediaitem.
 36. The computer system of claim 35, wherein the one or moreprograms include instructions for: while concurrently displaying theenlarged representation of the selected media item and the informationabout a source of the selected media item, detecting an input directedto a selectable user interface object that includes the informationabout the source of the selected media item; and in response todetecting an input directed to the selectable user interface object thatincludes the information about the source of the selected media item,initiating a process for displaying, in the first application, acommunication history for a conversation in which the selected mediaitem was shared.
 37. The computer system of claim 23, wherein: the mediaapplication includes a plurality of sections; and the one or moreprograms include instructions for: while displaying a first section ofthe plurality of sections of the media application, automaticallydisplaying the first shared media item in the first section of theplurality of sections of the media application.
 38. The computer systemof claim 23, wherein the one or more programs include instructions for:in response to a user input requesting to display the plurality ofshared media items, displaying the set of one or more media items thathave not been added to the media library.
 39. The computer system ofclaim 38, wherein the set of one or more media items that have not beenadded to the media library that are displayed in response to the userinput requesting to display the plurality of shared media items, aredisplayed without a visually distinguished appearance.
 40. The computersystem of claim 23, wherein the display criteria include one or more ofthe criteria selected from the group consisting of relevance criteria,location criteria indicating that a user of the computer system waslocated at a same location corresponding to the first shared media item,user identification criteria that indicates if a user of the computersystem appears in the first shared media item, and recency criteria todisplay media items that have been shared within a predeterminedthreshold amount of time.
 41. The computer system of claim 23, whereinthe one or more programs include instructions for: receiving, by thefirst application, a request to delete a communication thread in whichthe first shared media item that has not been added to the media librarywas shared; and in response to receiving the request to delete thecommunication thread, forgoing display of the first shared media item inthe collection of media items when the collection of media items isdisplayed.
 42. The non-transitory computer readable storage medium ofclaim 24, wherein displaying the collection of media items includes, inaccordance with a determination that a second shared media item from theset of one or media items that have not been added to the media librarymeets the first criteria, displaying the second shared media item in thecollection of media items concurrently with the second plurality ofmedia items, wherein the second shared media item is visuallydistinguished from the second plurality of media items based on thevisual feature that is separate from content of the second shared mediaitem.
 43. The non-transitory computer readable storage medium of claim24, wherein displaying the first shared media item that is visuallydistinguished from the second plurality of media items comprisesdisplaying the first shared media item with changed appearance of atleast a portion of a border region of the first shared media item. 44.The non-transitory computer readable storage medium of claim 24, whereindisplaying the first shared media item that is visually distinguishedfrom the second plurality of media items comprises displaying the firstshared media item with a content obscuring effect applied to at least aportion of the first shared media item.
 45. The non-transitory computerreadable storage medium of claim 24, wherein displaying the first sharedmedia item that is visually distinguished from the second plurality ofmedia items comprises displaying the first shared media item with agraphical element that is overlaid on at least a portion of the firstshared media item.
 46. The non-transitory computer readable storagemedium of claim 24, wherein the one or more programs includeinstructions that, when executed by the computer system, cause thecomputer system to: receive a sequence of one or more user inputsincluding a user input selecting a media item in the displayedcollection of media items; and in response to receiving the sequence ofone or more user inputs, display an enlarged representation of theselected media item and a plurality of controls for performingoperations associated with the selected media item, wherein: inaccordance with a determination that the selected media item is a mediaitem in the second plurality of media items selected from the medialibrary, the plurality of controls displayed with the enlargedrepresentation of the selected media item include a first set ofcontrols; and in accordance with a determination that the selected mediaitem is a shared media item from the set of one or more media items thathave not been added to the media library, the plurality of controlsdisplayed with the enlarged representation of the selected media iteminclude a second set of controls distinct from the first set ofcontrols.
 47. The computer system of claim 46, wherein the second set ofcontrols includes an indication that the selected media item is a sharedmedia item.
 48. The computer system of claim 46, wherein the second setof controls includes a control for adding the selected media item to themedia library.
 49. The computer system of claim 48, wherein the one ormore programs include instructions that, when executed by the computersystem, cause the computer system to: while displaying the enlargedrepresentation of the selected media item and the plurality of controlsfor interacting with the selected media item, receive an input selectingthe control for adding the selected media item to the media library; andin response to receiving the input selecting the control for adding theselected media item to the media library: add the selected media item tothe media library.
 50. The computer system of claim 49, wherein the oneor more programs include instructions that, when executed by thecomputer system, cause the computer system to: in response to receivingthe input selecting the control for adding the selected media item tothe media library: cease to display one or more controls for performingoperations associated with the selected media item that were displayedprior to receiving the input selecting the control for adding theselected media item to the media library.
 51. The computer system ofclaim 49, wherein the one or more programs include instructions that,when executed by the computer system, cause the computer system to: inresponse to receiving the input selecting the control for adding theselected media item to the media library: display one or more controlsfor performing operations associated with the selected media item in themedia library that were not displayed prior to receiving the inputselecting the control for adding the selected media item to the medialibrary.
 52. The computer system of claim 46, wherein the one or moreprograms include instructions that, when executed by the computersystem, cause the computer system to: display, concurrently with theenlarged representation of the selected media item, information about asource of the selected media item.
 53. The computer system of claim 52,wherein the one or more programs include instructions that, whenexecuted by the computer system, cause the computer system to: whileconcurrently displaying the enlarged representation of the selectedmedia item and the information about a source of the selected mediaitem, detect an input directed to a selectable user interface objectthat includes the information about the source of the selected mediaitem; and in response to detecting an input directed to the selectableuser interface object that includes the information about the source ofthe selected media item, initiate a process for displaying, in the firstapplication, a communication history for a conversation in which theselected media item was shared.
 54. The non-transitory computer readablestorage medium of claim 24, wherein: the media application includes aplurality of sections; and the one or more programs include instructionsthat, when executed by the computer system, cause the computer systemto: while displaying a first section of the plurality of sections of themedia application, automatically display the first shared media item inthe first section of the plurality of sections of the media application.55. The non-transitory computer readable storage medium of claim 24,wherein the one or more programs include instructions that, whenexecuted by the computer system, cause the computer system to: inresponse to a user input requesting to display the plurality of sharedmedia items, display the set of one or more media items that have notbeen added to the media library.
 56. The computer system of claim 55,wherein the set of one or more media items that have not been added tothe media library that are displayed in response to the user inputrequesting to display the plurality of shared media items, are displayedwithout a visually distinguished appearance.
 57. The non-transitorycomputer readable storage medium of claim 24, wherein the displaycriteria include one or more of the criteria selected from the groupconsisting of relevance criteria, location criteria indicating that auser of the computer system was located at a same location correspondingto the first shared media item, user identification criteria thatindicates if a user of the computer system appears in the first sharedmedia item, and recency criteria to display media items that have beenshared within a predetermined threshold amount of time.
 58. Thenon-transitory computer readable storage medium of claim 24, wherein theone or more programs include instructions that, when executed by thecomputer system, cause the computer system to: receive, by the firstapplication, a request to delete a communication thread in which thefirst shared media item that has not been added to the media library wasshared; and in response to receiving the request to delete thecommunication thread, forgo display of the first shared media item inthe collection of media items when the collection of media items isdisplayed.